Related
I have a nexus one running a stock 2.2 FRF91 that is rooted with via universal androot. When the update for 2.2.1 notification hit my phone I downloaded it by mistake. I did not install it but the files are still on the phone along with the update icon in my notification bar. When I go to it I now only have the option to restart on install. Not the other options like install later.
Does anybody know how to get rid of the downloaded files and make that notification basically go away. Back to the do you want to download and install this update one? I figured it would require finding the files via a file browser and deleting them. I looked around real quick to see if I could find what and where it downloaded but was not sure what was what. I did not want to delete the wrong thing.
I would really like to get rid of this icon in the notification bar if possible.
Try rebooting using quickboot. It'll give you 2-3 days of being free from the notification. It beats hitting "install later" every 10 mins. Its been working for me so far
Sent from my Nexus One using Tapatalk
Thanks but I am past that point. I do not have that option. When I open the bar I get that its downloaded and verified and all that stuff. Only option is to restart and install.
Well as I entered my last post the notication popped up on the screen and I hit install later. But I still have the icon in the status bar. That was not there before today but I got the update push a couple of days ago. After reading another thread on the site it seems like others have the same issue
instruction
albundy2010,
1. apply update (recovery doesn't apply it, and delete update from /cache)
2. open rootexplorer, go to /system/ , find file "check", edit 1 to 0
3. open /system/build.prop , edit
ro.build.id to frg83G
version realise to 2.2.2
build host to android-test-20.mtv.corp.google
description passion user 2.2.1 to 2.2.2
save and reboot, enjoy
Go find and download FOTAkill
Sent from my Nexus One using XDA App
Better yet, just install the OTA, and then root afterwards. No big deal. Should take all of 2 mins.
This is a very old thread fellas. Let it die.
Sent from my Nexus One using XDA App
I've looked and I couldn't find a direct solution, so I'm going to give birth to this thread.
Problem: I want (and have problems downloading) the OTA Ice Cream Sandwich update on my rooted Verizon Motorola Droid 4
I rooted my phone awhile back. Just today I received a message that the system update was available.
-I am able to download the update.
-I am able to begin installing the update.
-During the installation process, the yellow progress indication bar fills about 1/8 of the way, then I get the ! warning sign above the little android figure.
Here's what I've done so far to try and correct this problem:
-Restarted my phone
-Restarted my computer
-Downloaded and installed the latest Motorola drivers from the official Motorola website.
-I attempted* to un-root my phone using the Droid 4 Utility 0.4.
--I should note that in the log, there was a like that read:
rm failed for /data/app/com.noshufou.android.su-1.apk, No such file or directory
Click to expand...
Click to collapse
-Restarted my phone again
-Tried installing the update with still no luck
*It appears that all the Droid 4 Utility did was remove Superuser, though I could be wrong. However, if this is the case, I still have a rooted device.
Once again, I'd prefer to have the OTA update, and not a leaked/rooted version of ICS. There's a possibility I didn't unroot my phone all the way. Am I doing this right?
Thanks in advance for the help.
ICS hasn't been officially released for the D4 yet.
This morning when I woke up I received an "Update available" notification. I am able to download an update for my phone. After downloading the update, I receive another notification:
"Install update
Update (6.13.219.en.US) has been downloaded and is ready to install.
Installation will take up to 10 minutes. Upon completion the phone will power off than back on.."
So it absolutely did not occur to you that this is the "219" update which can be found in this (General) section as well as in the Android development section .
Please do take a look in the topics mentioning "update" or "219". You will find topics for rooted and stock phones regarding the 219 update and how to proceed.
Die Bruine said:
So it absolutely did not occur to you that this is the "219" update which can be found in this (General) section as well as in the Android development section .
Please do take a look in the topics mentioning "update" or "219". You will find topics for rooted and stock phones regarding the 219 update and how to proceed.
Click to expand...
Click to collapse
Thanks for your help. I'm slightly inexperienced. I was so excited when I saw the system update that I suspected it to be ICS. Albeit, my hunt continues.
it failed because u altered system files of some kind... its happening to me too. i downloaded the stock system app zip from here in hopes to replace the system apk's so the update will go through but i dont know how to replace the system files... is it as simple as copy and paste, do u have to copy it to the sd card then use a file explorer to copy and overwrite over the files? i dont want to mess something up
I did modify the build file in root/system in order to install a certain APP from the Google Play Store, but I made sure I went and reversed all of the changes I made. Could you please post where you got this file from?
http://forum.xda-developers.com/showthread.php?t=1608866&page=3
Stensin said:
I did modify the build file in root/system in order to install a certain APP from the Google Play Store, but I made sure I went and reversed all of the changes I made. Could you please post where you got this file from?
Click to expand...
Click to collapse
The original post has also been updated with a link to the original files, as well as more complete instructions.
http://forum.xda-developers.com/showthread.php?t=1608866
omniuni said:
The original post has also been updated with a link to the original files, as well as more complete instructions.
http://forum.xda-developers.com/showthread.php?t=1608866
Click to expand...
Click to collapse
but how do u copy those files from NOTE 2? i downloaded the file, extracted the files but i cant copy them to the system folder
copy them to your phone via usb, make sure you are rooted, and CAREFULLY COPY them using a root explorer. You can get a good one from AntTek for free on the Play Store.
I tried that.. copied the files to the sd card. I can see them when i browse the sd card via the computer but when i unplug the cord they arent there anymore. Would replacing the stock boot animation via rom manager have anything to do with the fail?
Sent from my DROID4 using XDA
remember that the "sd card" the computer sees is the phone's internal storage. your actual sd card, as the computer sees it, is referred to by the phone as "sd-ext" or "external sd card" usually.
I did the samething, I changed two files and got help from this forum to get the originals. I use es file explorer in root and copied the files to where they need to be. I checked the permissions and rebulit the checksum for each file. After that I used voodoo to save my root. I rebooted instal from sdcard and it worked. hope this helps.
well it wasnt an app that i deleted.. i was reading somewhere about the build.prop file being messed up from using rom manager so i downloaded a new copy and pasted it over the old one and the update went through! thanks everyone!
Montecarlo97z said:
well it wasnt an app that i deleted.. i was reading somewhere about the build.prop file being messed up from using rom manager so i downloaded a new copy and pasted it over the old one and the update went through! thanks everyone!
Click to expand...
Click to collapse
I tried doing this, but it didn't work. Could you post the build.prop file that you used?
EDIT:
I was copying my build.prop file incorrectly. More details here.
I have a rooted KFHD. I cant seem to sideload certain apps. Rainy Days, Capital One Banking, FlightAware, HAR, and some others. Can someone please help?
wing-zero said:
I have a rooted KFHD. I cant seem to sideload certain apps. Rainy Days, Capital One Banking, FlightAware, HAR, and some others. Can someone please help?
Click to expand...
Click to collapse
can any1 help?
What happens when you try it?
Sent from my rooted Kindle Fire HD
ayaxxa said:
What happens when you try it?
Sent from my rooted Kindle Fire HD
Click to expand...
Click to collapse
application installation failed
Click to expand...
Click to collapse
I have tried getting older versions of the apks but that did not work
wing-zero said:
I have tried getting older versions of the apks but that did not work
Click to expand...
Click to collapse
If it does not install copy it to /system/app and set permisions to rw-r-r
Sent from my KFTT using xda app-developers app
Thanks for responding. Ok , copied to /system/apps, changed permissions to rw-r-r. Still will not install. Same error message running apks.
I have had problems installing some applications one I use a lot Paypal. The application won't install via sideload, or moving to system/app. I guess some applications are just not compatible at least for the moment. I've noticed a lot of games have problems as well even if they are installed.
wing-zero said:
Thanks for responding. Ok , copied to /system/apps, changed permissions to rw-r-r. Still will not install. Same error message running apks.
Click to expand...
Click to collapse
you don't install it you re boot sorry I was not clear enough about that
Sent from my KFTT using xda app-developers app
On re boot, nothing changed. Funny thing bout this is, this is the same android version on my kids Nabi2, and I was able to side load it there. So it leads me to believe its a kindle fire issue. Maybe....
Any one care to chime in
I'm having trouble with some side loaded apps on the fire HD. I don't think the ICS on the fire is quite standard. Amazon modified it quite a bit. I think this is where some of the problems lie.
I haven't tried this cause I don't have another tablet with ICS. Did you try pulling the apps from the nabi and pushing them to the fire with Adb. I wonder if that might work.
thedeester1 said:
I'm having trouble with some side loaded apps on the fire HD. I don't think the ICS on the fire is quite standard. Amazon modified it quite a bit. I think this is where some of the problems lie.
I haven't tried this cause I don't have another tablet with ICS. Did you try pulling the apps from the nabi and pushing them to the fire with Adb. I wonder if that might work.
Click to expand...
Click to collapse
How do i push an app in adb
i tried " adb install app.apk" and get this....
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
found the solution here, have to add gmap library etc
http://forum.xda-developers.com/showthread.php?t=1382925
When an OTA update becomes available, there is a recurrent notification prompting to upgrade.
The below method tricks the OS into thinking that it is already at the latest version, in effect stopping the update notification from appearing.
I am not responsible for anything you do with your device.
Pre-requisite
Device must be rooted
Steps
Download FOTAKill apk
Put the apk in "/system/app"
Set proper file permissions (644, or rw-r--r--) for the apk
Clear "/cache" (e.g. boot into CWM and clear cache)
Reboot
Check "Settings > About tablet > System updates" and it should show "up to date" now.
Note that after rebooting there may still be a notification to update, after clearing no further notification will appear.
Rollback
To re-enable OTA update notification, delete the apk and reboot!
iamelton said:
lately since Android 4.2 OTA update became available for my device, there was a recurrent update notification prompting me to update..
as i dont want to upgrade yet due to app incompatibility issues not being resolved, i asked for help and was given a solution after searching and reading some posts..
it worked for me and i would like to share it here as i found that there were other users looking for a solution like i did..
ur device needs to be rooted to follow the steps below..
steps:
(1) download FOTAKill (firmware over-the-air kill) apk
(2) put the apk in "/system/app" with a file explorer
(3) set proper file permissions (644) for the apk
(4) clear "/cache" (i booted into CWM and cleared cache there)
(5) reboot
(6) check "Settings > About tablet > System updates".. should tell you "up to date" now..
note that after rebooting i still got a notification on update, but after clearing it there was no further notification since then..
Click to expand...
Click to collapse
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Worked great, better than messing around with Google services framework.
Another possibility to get rid of OTA updates reminders on 4.1.2:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
OR... download Autorun manager from the Play store and disable the following in Services( must enable system settings in preferences)
Receiver com.google.android.gsf.update.SystemUpdateService
Requires root access
wilx said:
Thanks,worked great, I didn't even need to clear the cache. On reboot, it said updating.... I panicked for a second, but it only reported for a coupe of seconds, then once booted, it said update available. I cleared the message and now the update has gone! In about phone - system update it reports upto date
Click to expand...
Click to collapse
Same here thank you iamelton!
andro54 said:
Same here thank you iamelton!
Click to expand...
Click to collapse
Same here didn't need to clear cache. The whole thing took about 30 seconds.
Thank you
Sent from my Nexus 7 using xda app-developers app
the clear cache part is for those who might have already downloaded the update package file (which is about 80MB) by the ota service.. it removes this file and frees up some cache space..
What does FOTAkill actually do to your system?
Sent from my Nexus 7 using Tapatalk 2
ExploreMN said:
What does FOTAkill actually do to your system?
Click to expand...
Click to collapse
That's a GREAT question.
iamelton do you know the specifics? It would also be interesting to know what permission if any are effected with this method.
Sent from my Nexus 7 using xda app-developers app
sorry but i have no idea what it actually does to the system, apart from the obvious function of stopping the OTA service..
from this page, it requires the following permissions..
Code:
android.permission.RECEIVE_BOOT_COMPLETED
com.google.android.providers.gsf.permission.WRITE_GSERVICES
com.google.android.providers.gsf.permission.READ_GSERVICES
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
datorprofessor said:
It worked. I follwed your insttrucction. I made file permission to 755 instead. Is there any different? I already had 4.2 but not that one with multi user. I think the update will partition the SDcard, but maybe it already did from 4.1.2 to 4.2 with sdcard0 and emulated. That iswhat I already have. But not the multiuser. I was wondering if it will also block update 4.3 4.4 etc? ??
Sent from my Nexus 7 using xda app-developers app.
Click to expand...
Click to collapse
afaik it should stop any future OTA updates regardless of android versions..
and granting permission 755 is more than the needed 644, but that does no harm..
i thought 4.2 was the version with multi-user support, but then im not on 4.2 yet so cant tell much about it..
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
gelhack said:
What Google did with OTG / Stickmount / DirectoryBind on 4.2 was a real buzz kill, so I don't want it now
either. I'm not going to hold my breath on this, but I'm hoping that some future update might allow real
data sharing on a USB stick, so I might eventually want to do an update. My question is this:
If I install FOTAKill to stop the notices etc, will uninstalling it allow me to update again?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i think removing the apk from /system/app/ should allow OTA notifications to show again, though i have not tried it yet..
btw, we have the same reason as why not to upgrade..
I used this from other thread, forgot where it is.
"Install Autostarts app.
Go to "After Startup"
Scroll down until you see "Google Services Framework"
There should be several of them. For me it was the third one. Touch it and read the bottom of the popup to find out. It will say "Receiver com.google.android.gsf.update.SystemUpdateService. ....(you get the point)
Disable it. Done..."
Peaceful on 4.1.2.
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
helloterence said:
There's another alternative way that I used that worked:
In the file "/system/build.prop" find the string starting "ro.build.fingerprint" and after symbol "=" add the following "google/nakasi/grouper:4.2/JOP40C/XXXXXX:user/release-keys"
Instead of XXXXXX place the figures from the string "ro.build.version.incremental"
Make the nandroid backup prior to this.
For editing file use Root Explorer.
After editing - reboot and connect to the Internet - the reminding should stop.
Click to expand...
Click to collapse
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
iamelton said:
thx for ur method..
i suspect this method only applies to the OTA of android 4.2, which means future OTA alerts of, say, 4.2.1 will pop up again..
Click to expand...
Click to collapse
Nope. I'm still on 4.1.2 and haven't gotten any notification about 4.2.1.
I'm assuming that updates to 4.2 and 4.2.1 are incremental, and as such you couldn't install or get a notification for 4.2.1 until you installed 4.2. So any method that stopped 4.2 notices would also stop 4.2.1 notices.
Sent from my Nexus 7 using xda app-developers app
I personally like the stock android browser for quick internet (not to mention that it supports flash). I tried to copy the browser.apk file from another device and transfer it to my KF HD 7", but when installing got a message saying "Parse Error" - There is a problem parsing the package. So, obviously that method will not work.
Does anyone out there have a method to get the stock android browser onto the KF HD 7?
Thanks in advance!
You need to push it or copy it to the /system/app folder, and give it root permissions.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
Ph0enix_216 said:
You need to push it or copy it to the /system/app folder, and give it root permissions.
Click to expand...
Click to collapse
Thanks for your reply. I had already moved the .apk file to the /system/app folder and attempted to run it there. That's when I got the parse error described above. It did not ask for root permissions, so I wasn't able to grant them. Unless there is something else that I am missing?
Thanks again for your help!
LeiraHoward said:
Thanks for your reply. I had already moved the .apk file to the /system/app folder and attempted to run it there. That's when I got the parse error described above. It did not ask for root permissions, so I wasn't able to grant them. Unless there is something else that I am missing?
Thanks again for your help!
Click to expand...
Click to collapse
There shouldn't be a superuser request. To install the stock browser, first:
a.) Move it to /system/app
b.) Give it root permissions from there like this: rw-r--r--. You can do this in an app like ES File explorer by holding the app and selecting "permissions." Just check the boxes that apply.
c.) Reboot--the app will probably crash if you try to launch it without restarting your system. After the Kindle reboots, try the app to make sure it works. This method is how you move any app to the /system/app folder and make it work correctly (although some won't work if you do this).
Hope this helped. If you have anymore questions, go ahead and ask
Ph0enix_216 said:
Hope this helped. If you have anymore questions, go ahead and ask
Click to expand...
Click to collapse
Thanks for the instructions. (And sorry for the delay getting back to you). I didn't get a chance to try this until just now.
Unfortunately, I'm still not able to get this to work. I keep getting the Parse Error when I attempt to install the .apk. I double checked everything, and the permissions are fine, and I restarted the Kindle Fire, and still no luck. I can only think of two things that might still be the issue:
(1) I got my browser.apk from a Jellybean 4.2 version of Android, it is possible that it is too new for the Kindle Fire version. (Not sure where I could get an older version, though).
(2) Amazon may just not play nicely with normal .apk files.
Yea you usually get a parse error if its for a newer version of android.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Yea you usually get a parse error if its for a newer version of android.
Click to expand...
Click to collapse
Any idea where I could pick up a clean copy of an older version? I'm actually not sure what version of android Amazon Kindles are running.
Kindles run ice cream sandwich based os, I don't know offhand where you could get a copy without having to download a ROM and extracting the apk from it without flashing it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Kindles run ice cream sandwich based os, I don't know offhand where you could get a copy without having to download a ROM and extracting the apk from it without flashing it.
Click to expand...
Click to collapse
Thanks... I just realized that my husband's android phone runs ice cream sandwich... I'm going to try to get the browser.apk file from him when he comes home tonight. If that doesn't work, I'll try grabbing it from a ROM. Thanks again.
LeiraHoward said:
Thanks... I just realized that my husband's android phone runs ice cream sandwich... I'm going to try to get the browser.apk file from him when he comes home tonight. If that doesn't work, I'll try grabbing it from a ROM. Thanks again.
Click to expand...
Click to collapse
Someone uploaded the stock AOSP Browser.apk on the Kindle Fire HD Themes & Apps forum a while back, which was pulled from a phone running ICS or something. I attached it at the bottom. I had it working fine on my Kindle when I was running stock OS. All I did was move it to my SD card, push it to "/system/app," and grant it root permissions. I had to do it this way, as it would force close if I tried to install it the normal way.
And Amazon does play nice with some .apk files. It's just a matter of finding the right ones. Unfortunately, you can't know until you install it as to whether or not it works or not.
Ph0enix_216 said:
Someone uploaded the stock AOSP Browser.apk on the Kindle Fire HD Themes & Apps forum a while back, which was pulled from a phone running ICS or something. I attached it at the bottom. I had it working fine on my Kindle when I was running stock OS. All I did was move it to my SD card, push it to "/system/app," and grant it root permissions. I had to do it this way, as it would force close if I tried to install it the normal way.
And Amazon does play nice with some .apk files. It's just a matter of finding the right ones. Unfortunately, you can't know until you install it as to whether or not it works or not.
Click to expand...
Click to collapse
Thanks. I somehow or another missed the notification of your reply, so just now got around to downloading and attempting to install this version of browser.apk. Unfortunately, it doesn't work for me, either. It fails in a different way, gets part way through the install process and then just gives me a message saying "Application not installed." *sigh* Ah well. Thanks for your help anyway!
Ph0enix_216 said:
Someone uploaded the stock AOSP Browser.apk on the Kindle Fire HD Themes & Apps forum a while back, which was pulled from a phone running ICS or something. I attached it at the bottom. I had it working fine on my Kindle when I was running stock OS. All I did was move it to my SD card, push it to "/system/app," and grant it root permissions. I had to do it this way, as it would force close if I tried to install it the normal way.
And Amazon does play nice with some .apk files. It's just a matter of finding the right ones. Unfortunately, you can't know until you install it as to whether or not it works or not.
Click to expand...
Click to collapse
I was finally able to get it working... I went back to the forum you mentioned and found an older version of the browser.apk that finally worked. Still won't "install" and I can only access the browser from an app manager software, not the KFHD system, but it exists. Thanks!