Related
Hey everyone, I'll up front say I'm more a user than a tweaker, so right now my NC (and my wifes) work awesome. I am currently on CM7, but my wife and many folks need to use the stock ROM and until a clean way to update with autonoot and such comes out, hopefully this is useful.
Clockwork Mod won't install an OTA, but I have a feeling that it'll still download it and try to install it, and I'm afraid it will try to install it over and over as long as the file is there. So moving to CWM to avoid the OTA is out.
Renaming otacerts doesn't work, lots of accounts of that.
But in my experience, OTAs always compare the build prop to see if they need to OTA, so what I'm going to do to my NC and my wifes NC is modify the build prop to the new settings and see if that avoids the OTA.
BTW, I know Nookie Froyo, CM7 etc won't OTA, etc, so now that's out of the way....
Due to multiple reports that using Root Explorer has somehow screwed up the system requiring users to manually re-copy their old build.prop back, I suggest you DO NOT use Root Explorer to do this.
First thing is look in /media for the uploader, in case it's already downloaded. Delete it if it's there! If you're paranoid, check when you're done with the following too, just in case it snuck in while you were editing
Get the new build.prop from here:
If you're still on Eclair: http://dl.dropbox.com/u/334233/build.prop-1.3.0-eclair
If you're on Froyo: http://dl.dropbox.com/u/334233/build.prop-1.3.0-froyo
Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system
Push the new build.prop to your system
Code:
adb push build.prop-1.3.0-[COLOR="Red"]YOURBUILD[/COLOR] /system/build.prop
Note you need to replace YOURBUILD with the appropriate build, Froyo or Eclair, or whatever you named the build.prop..
Now your NC should have thew new build.prop, so now reboot. When you reboot, you should get a pop-up message with a green N saying you've updated to 1.3, but you should not see any update progress dialogs or any indication there was an actual update. Hopefully this makes it not try to OTA to 1.3.0! Please report back! It worked for 1.0.1 with the 1.1.0, as well as the 1.2.0 update out there, and it should work for 1.3.0.
Below is for old 1.2.0 information, don't use this unless you're sure you need to!
Get the new build.prop from here: http://dl.dropbox.com/u/334233/build.prop-1.2.0
Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system
Push the new build.prop to your system
Code:
adb push build.prop-1.2.0 /system/build.prop
Once I get a little feedback on this, I'm going to move it to the NookDevs wiki, just don't want to put nonsense there if that's what it is I've done this to both my NC and my wifes, no problem so far, and hopefully it avoids the OTA.
done - we'll see what happens next ....
newbie
Hello
I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise
JF-WS6 said:
Hello
I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise
Click to expand...
Click to collapse
I'll keep revising the instructions in the first post, but that's so far the only theory that hasn't failed yet... So get adb to work and follow the instructions. You can do it over Wifi, so even if USB isn't working out for you due to your OS, the Wifi ADB widget on the Market will work.
How to use ADB itself, you can google.. It's fairly straightforward. Basically you'll just need to adb connect ip : port once you know it, the Wifi ADB widget tells you when it sets up.
FYI, I just did all of this from Root Explorer on the device. I snagged yer file from your dl.dropbox link, copy it over via root explorer, and set the rights. When I restarted, the little green n told me I had recently updated.
Maybe we can bypass optional future updates by changing our version to something really high like 1.99?
Yes I know I never say anything on here but will now. I have used something like this on before I I do think this will work just fine as the Nook already things it's updated so when it checks it's going to see that it is already updated.
Now as to what BN will do in a week or so who knows. We just need some more support for roms and so on for the nook and we will be good to go.
ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.
Used your download link to install it. Says I updated to 1.1.0. Thanks
danguyf said:
ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.
Click to expand...
Click to collapse
Um, yeah... Let me explain further I guess?
B&N Components decide it needs an update, downloads it
B&N components see the update is downloaded, sets up the OTA update, reboots
Clockwork Recovery does NOT update
System boots
Repeat step 2 - 5 forever?
That's what I meant by "Clockwork won't install an OTA" and such.
MattJ951 said:
Used your download link to install it. Says I updated to 1.1.0. Thanks
Click to expand...
Click to collapse
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.
khaytsus said:
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.
Click to expand...
Click to collapse
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.
bdcrim said:
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.
Click to expand...
Click to collapse
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
khaytsus said:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
Click to expand...
Click to collapse
Thanks again.
khaytsus said:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
Click to expand...
Click to collapse
I just checked the about settings and it also says 1.1.0 . If im on 1.1.0 I don't really mind since my device is still rooted and works identically to how it did a day ago. I'm guessing it pulls the about settings pulls the data from the build.prop every reboot
Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).
skaman77 said:
Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).
Click to expand...
Click to collapse
Good thought. Do you want to flip a coin or draw straws?
As soon as I saw the thread about the 1.1.0 update today, I turned my WiFi off. There was no zip file in my /media folder or on root when I made the changes to the build.prop file. When I rebooted, I received a notice in the bar that my Nook Color software had been updated. WiFi is still off, but I am going to turn it back on and see what happens.
i also updated file lines thru root explorer and gave me massage that i had been updated. crossing fingers
Hello Everyone,
So I unfroze all of my apps in Titanium Backup and flashed the OTA that is posted in the development forum for the Droid 3 and it seems to have worked great other than one small problem. Every time I try to use the camera or camcorder they will open for about 2-3 seconds and then they close and I end up back at my home screen. Does anyone have any ideas on what I can try to make my camera apps work again?
EDIT: Sorry, forgot to mention that I did try rebooting the phone as well as clearing the cache for the camera app, no change. Also Camera Zoom FX stays open but just has black where the camera image would normally be.
Thanks!
Maybe you... forgot to unfreeze the camera app lol.
No but id check what you do have frozen, maybe there's a service the camera app is dependent upon you might have accidentally frozen (assuming you rerooted after update)
Sent from my DROID3 using Tapatalk
I did re-root after applying the OTA update and then I froze about 15 apps that I found to be annoying/un-needed, however even after unfreezing all of them, any app involving the camera still isn't working. I also just noticed that my flashlight app that worked before the OTA is not working either.
First thing I would try is "clear data" for the Camera app and reboot.
rtbrjason said:
First thing I would try is "clear data" for the Camera app and reboot.
Click to expand...
Click to collapse
Tried that a couple of times but no change. I just also noticed that the camera app flashes a small message up at the bottom of the screen really quickly stating that the camera is unable to initialize.
Uninstall any third-party app that uses the camera (if you have any) the try again.
kishin14 said:
Uninstall any third-party app that uses the camera (if you have any) the try again.
Click to expand...
Click to collapse
Thank you for the suggestion, I hadn't thought of that. Unfortunately that did not work either. No change, still getting the same message for about a second or two and then it closes.
Try re-uploading the camera apk and odex files, might need to set permissions the same as the other system apps.
Unzip and use something like rootexplorer, delete current BlurCamera.apk and BlurCamera.odex, set write access on system/app folder then copy these.
-smc
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
limaxray said:
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
Click to expand...
Click to collapse
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
640k said:
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
Click to expand...
Click to collapse
I agree, and would suggest to anyone to use the script for removing and replacing the bloat - it makes it much easier to do (especially from adb when you foul it up) and keeps track of what you've done.
That said, I highly doubt that is the issue here. The update script first checksums everything that needs to be patched and deletes everything that is to be replaced. So if you have anything removed, it will either cause it to fail (if the file is to be patched) or not matter (if it is to be deleted or simply isn't touched). In other words, if you have anything missing that is needed, the update wouldn't touch anything.
Furthermore, I don't think any of the commonly removed bloatware serves as a dependency for the camera. At least not as far as I can tell.
I can tell you that /system is filled to the brim with all of the bloatware. The current ROM is just barely shoehorned in there. Many 'for-root-users' apps like to install stuff to /system and since the updater script doesn't check for free space, it may very well fail to extract in the middle of execution even though it already deleted a bunch of files.
So I think more importantly than restoring bloat, you should remove anything you added.
I tried your directions and re-ran the update after fixing recovery, however my camera still doesn't work because of the same basic issue, running out of space before the update completed. Upon re-rooting and going in to my system directory with root explorer I noticed that I now only have 195k free there. I checked the xbin folder and do not see busybox or anything else there that I recognize that I could delete to free up space. How can I tell what is safe to delete and what isn't so I can free up enough to fix my recovery again and hopefully get the update to work properly?
You can see a breakdown of disk usage with this command:
Code:
du -sh /system/*
Here's mine with busybox removed:
Code:
147.6M /system/app
7.5M /system/bin
11.0K /system/build.prop
5.5M /system/etc
5.1M /system/fonts
35.5M /system/framework
75.7M /system/lib
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
135.0K /system/xbin
And my free space is
Code:
$ df /system
Filesystem Size Used Free Blksize
/system 320M 317M 2M 1024
Other than su, the only files you need in xbin are (don't worry about the symlinks)
Code:
backup dexdump drm1_func_test run_backup run_restore ssmgrd
I think the only extra bits I now have on /system is su.
I also found the system dump from this post to be very helpful.
Whenever I'm trying du It's saying that the command wasn't found. What are you using for your terminal access?
Hmm it seems du isn't a standard binary even though I have it in bin. I sure don't remember putting that in there...
Anyway, I use adb or Better Terminal Emulator Pro, depending what mood on in.
To use adb, you'll need to install busybox to /data somewhere (I have mine in /data/local/bin) and use
Code:
$ /data/local/bin/busybox du -sh /system/*
BTEP has a fairly complete set of CLI tools included - such as du - so you don't need busybox.
I figured out how to do the command through busybox and have come up with some interesting results...
I am over yours on...
Code:
153.8M /system/app
1.9M /system/xbin
I am under yours on...
Code:
4.7M /system/bin
4.9M /system/etc
71.8M /system/lib
And I match yours on...
Code:
11.0K /system/build.prop
5.1M /system/fonts
35.5M /system/framework
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
This is with busybox installed in the xbin folder so that is probably why I am over on that one, however the app folder is quite a bit over as well but I can't figure out why. The only file that I can find in there that doesn't seem to belong is Superuser.apk but it is only 191k.
UPDATE: I finally found a large app that wasn't present in the system dump that you had mentioned before. I backed it up to my sd card and removed it, went through the update, and now my camera is working. Thank you very much to everyone who helped, especially limaxray!
Glad I was able to help!
This is a great example for why we should always wipe data/cache before any rom update.
dsw361 said:
This is a great example for why we should always wipe data/cache before any rom update.
Click to expand...
Click to collapse
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
limaxray said:
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
Click to expand...
Click to collapse
Exactly. the last thing I would do is wipe data/cache if we encountered a bootloop. Adb is so important to us right now because we don't have a custom recovery or an sbf.
Sent from my DROID3 using Tapatalk
Got the new one for 5.7.906 rooted and dled script manager
when I run psouza4's script after answering questions about what I wanted to keep
It froze right away saying myverizon.apk was read only or something
rebooting... reboot not permitted.
so.. I figured I'd just change that one manually.. changed it, ran it again.. and it froze saying file not found...
so i edited to script to remove that one command/file..
ran it again and i got
"working please wait.....
reboot: operation not permitted"
so I was going to go the titanium route but I can't afford pro version.. also reading through psouza4's thread it notes that some apps will circumvent freezing and load anyway unless renamed..
[q1] does anyone else have this problem with script and if so what was the fix?
[q2] if I have to rename everything manually (a huge pain in the arse) what are the names of the *.apk's associated with
home launcher, motorolas text messaging, widgits, swipe keyboard, ect.. in his list so i don't accidentally remove them?
Thanks!
production said:
Got the new one for 5.7.906 rooted and dled script manager
when I run psouza4's script after answering questions about what I wanted to keep
It froze right away saying myverizon.apk was read only or something
rebooting... reboot not permitted.
so.. I figured I'd just change that one manually.. changed it, ran it again.. and it froze saying file not found...
so i edited to script to remove that one command/file..
ran it again and i got
"working please wait.....
reboot: operation not permitted"
so I was going to go the titanium route but I can't afford pro version.. also reading through psouza4's thread it notes that some apps will circumvent freezing and load anyway unless renamed..
[q1] does anyone else have this problem with script and if so what was the fix?
[q2] if I have to rename everything manually (a huge pain in the arse) what are the names of the *.apk's associated with
home launcher, motorolas text messaging, widgits, swipe keyboard, ect.. in his list so i don't accidentally remove them?
Thanks!
Click to expand...
Click to collapse
Ensure usb debugging is on under development in application settings. Verify you are rooted, if not, only motofail will root 906. Else, try using a root browser, or manually make /system and /system/app writable before running the script.
Skreelink said:
Ensure usb debugging is on under development in application settings. Verify you are rooted, if not, only motofail will root 906. Else, try using a root browser, or manually make /system and /system/app writable before running the script.
Click to expand...
Click to collapse
root = verified
/system and /system/app set to R/W
usb debuging = on
used modified script removing all instances of 2>/dev/null and reboot command
now I'm getting *.apk not read/writable
confirm that /system and /system/app it set to read/write and when i hit properties.. only the read box is checked.. so i go to change it again.. and the other boxes (read,write,execute) are already checked... I don't understand.
I have the newest version of busy box installed I know he changed the syntax after v1.182 but I can't seem to find a copy of that version.. maybe thats the problem? ugh..
production said:
Got the new one for 5.7.906 rooted and dled script manager
when I run psouza4's script after answering questions about what I wanted to keep
It froze right away saying myverizon.apk was read only or something
rebooting... reboot not permitted. !
Click to expand...
Click to collapse
When you loaded the script into script manager, did you check the select to allow the script to run with SU permissions? in other words, you start script manager, you load the debloat script, there are a bunch of options available before you hit the "run" button, one of which allows the script to run with root permissions. My guess is that you missed that, based on what you are describing.
Thanks to everyone who contributed.. :good:
got it to work.. It was afterall allowing to run the script as root as doogald suggested.. can't believe i missed that.
THANKS
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
Hello!
I'm on a rooted Cricket Android 4.4.2 device.
ROM Version: 1.11.506.1
Software Number: 1.11.506.1
HTC Sense 6
Baseband: 1.101.1372.19
Can somebody please tell me how to get rid of the annoying software update that has been coming the last week?
Is there way to somehow either change my software number to trick the phone into thinking I'm updated or perhaps I should update? If so, how?
I appreciate the help.
Using a root file explorer and freezing the updater app manually would probably be the safest (personally I like Root Browser by JRummy hasn't been updated in awhile but if ain't broke it don't need to be, and it is a tool I know will always perform these critical tasks correctly)
By freezing the the system updater app in the following way, you will be able to easily reverse the process using the same process. While there are some mods that can hide the notification itself (eg.: Xposed FW), this method completely disables the update check process, thus freeing up system resources. Twofold if you look at it this way imo, rather than adding potentially harmful additional resources.
# Open your root fs explorer
# navigate to fs root:
/
# then to:
/system/priv-app
# locate the file:
Updater.apk
# append ".bak" to the file name. In other words rename it to:
Updater.apk.bak
# note: no need to mess with it's .odex file, it never hurt no one. Also depending on your fs explorer and personal settings, the app's icon thumbnail has likely changed to a blank white square/unkown/generic file icon and is totally normal.
# profit and celebrate the newly liberated space in your notifications and don't forget to miss that pesky "remind me later" pop up.
#should there be an update that your are feeling compelled to (try) and install simply remove ".bak" from the files name and proceed as usual. Note that the only thing you should be changing in all this is +/- ".bak" from the file name. Don't go trying to change this or other apps file name. It don't work like that. Speaking of other apps, I urge great caution against going ape$#¡+ and doing this carelessly, especially for apps anywhere under "/system".
# The Disable button on the App Info pages should be the primary resource for disabling apps for most users. Know what the app does and is used for on your system BEFORE making changes or worse yet, deleting it.
~/#: print <INSERT STANDARD DISCLAIMER, AKA CYA STATEMENT HERE>
Don't just say it, hit that thanks button if I helped you in any way!!!
Sent from my HTC Desire 510 using Tapatalk
wow thank you so much :laugh:
jackunoff said:
Using a root file explorer and freezing the updater app manually would probably be the safest (personally I like Root Browser by JRummy hasn't been updated in awhile but if ain't broke it don't need to be, and it is a tool I know will always perform these critical tasks correctly)
By freezing the the system updater app in the following way, you will be able to easily reverse the process using the same process. While there are some mods that can hide the notification itself (eg.: Xposed FW), this method completely disables the update check process, thus freeing up system resources. Twofold if you look at it this way imo, rather than adding potentially harmful additional resources.
# Open your root fs explorer
# navigate to fs root:
/
# then to:
/system/priv-app
# locate the file:
Updater.apk
# append ".bak" to the file name. In other words rename it to:
Updater.apk.bak
# note: no need to mess with it's .odex file, it never hurt no one. Also depending on your fs explorer and personal settings, the app's icon thumbnail has likely changed to a blank white square/unkown/generic file icon and is totally normal.
# profit and celebrate the newly liberated space in your notifications and don't forget to miss that pesky "remind me later" pop up.
#should there be an update that your are feeling compelled to (try) and install simply remove ".bak" from the files name and proceed as usual. Note that the only thing you should be changing in all this is +/- ".bak" from the file name. Don't go trying to change this or other apps file name. It don't work like that. Speaking of other apps, I urge great caution against going ape$#¡+ and doing this carelessly, especially for apps anywhere under "/system".
# The Disable button on the App Info pages should be the primary resource for disabling apps for most users. Know what the app does and is used for on your system BEFORE making changes or worse yet, deleting it.
~/#: print <INSERT STANDARD DISCLAIMER, AKA CYA STATEMENT HERE>
Don't just say it, hit that thanks button if I helped you in any way!!!
Sent from my HTC Desire 510 using Tapatalk
Click to expand...
Click to collapse
I'm gonna chime in here and I know you're trying to help but this really isn't helping because you didn't actually freeze the app like you said. All you did was change the apps name so now when the system actually calls upon that app it's simply going to error out and actually cause it to use more resources and not less as you said albeit it will not show up anymore but that's not the way to stop it! If I go into /system/priv-app and change Phonesky.apk to Phonesky.apk.bak the play store is going to break and then send me the error to my screen every second until I fix it and that uses more resources and the only reason you're not seeing the error on the screen for the Updater is because it's doing it behind the scene in a log. Now the real way to stop this app is to actually really freeze it or uninstall it so the system actually knows the app is no longer there and there are plenty of apps in the play store that can do that.
---------- Post added at 06:17 AM ---------- Previous post was at 06:16 AM ----------
Khiddfrost said:
wow thank you so much :laugh:
Click to expand...
Click to collapse
You should read my post above.