Related
Is there any way to cancel the download of the OTA Gingerbread update?
I'm on 2.3.340.MB10, Baseband BP_C_01.09.07P, rooted, stock ROM. I manually triggered the update check earlier (About phone→System updates). I got the update notice and selected “Later” (I want to wait until it's clear that I can keep or regain root).
Maybe an hour later, I noticed a download icon. The notification says Downloading updates and is currently at 18%. I went into Airplane mode to stall it. I tried rebooting and turning Airplane mode on and off, but the best I can do is stall the download and I can't stay in Airplane mode forever. (WiFi has been off the whole time.)
When I go back to System updates, I get “An update is currently downloaded. You will be notified when the download is complete.”
Can somebody please provide me one of the following:
1. How to cancel the download
2. How to indefinitely not install after allowing the download to complete
3. How to upgrade and keep or regain root
Thanks!
P.S.: Does anyone know why the download started when I picked the Remind me later option?
not sure about the first two questions, but as for the 3rd one, P3droid posted rooted OTA build with instructions in DX section of his forum. I don't think links are allowed, but shouldn't be too hard to find.
Oh and yeah, downloading the update automatically after it's found is default behavior for DX.
Can't cancel, but after download it will ask you if you want to install now or later. Choosing later is your only option, unfortunately you will be reminded every four hours if you want to install or not
Sent from my DROIDX using XDA App
Settings
Battery and Data Manager
Data Delivery
Social Applications
Sync over Wi-Fi Only <- Check this box
Thanks, all!
Thanks, folks who posted.
tech_head's tip indeed froze the download, since I rarely connect to WiFi. (Why updates are “Social Applications,” I don't know.) (Interestingly, I had the hardest time actually getting into this menu. Took about 10 tries.)
metamorphousthe's tip saved me from being paranoid about the download completing.
meshdub's tip I haven't checked into yet, but that's promising.
Thanks again!
Just delete a system app and the update will fail when it tries to install and then you're all set
I renamed the blurupdater.apk to .bak I think that stops updates.
larsdennert said:
I renamed the blurupdater.apk to .bak I think that stops updates.
Click to expand...
Click to collapse
You should be all set
Many of us have know that the newest update that was push 2.0.5 break root. Well, for those who didn't know, now you know. Let's me be clear, there is NOTHING TO BLOCK THE OTA UPDATE, unless you build your own firewall. That said, the mod that we had was to use sql and turn automatic OTA into manual thus unless you were looking for it, it shouldn't. Or something you did may accidentally turn it back to automatic.
That said, we had one report of successful revert back to the older firmware here from 2.0.5. I have made a suggestion to manually force the system to fail the boot 8 times and do a full wipe. And this should revert it back to the original firmware that came with the Nook HD/HD+. Well, in the future, this may no longer be the case, as newer Nook may come with 2.0.5 out of the box, but let's do this one step at a time, we aren't there yet and maybe better solution will come later. So, if you accidentally updated to 2.0.5, you should try the following.
Backup your naughty stuff that's on the internal storage (even if they are not naughty, do it so anyway)
Force the nook to fail at least 8 times. First you power the device off then hit the power button, and when it's trying to boot, hold on to the power button, and I think about 10sec after it will force poweroff. You timing have to be quite good and make sure it's not getting a success boot. You basically have to do that at least 8 times.
If you successfully did all that, it should revert back to the original firmware. I know that the 8 boot loop will reset it back to 2.0.0 from 2.0.2 because I did that before.
Try rooting it again.
I hope this help.
Interesting, I'm going to try and force the 8-loop reboot and set if I can get back to 2.04. I think then I also have to skip the out of box registration process as this automatically updates?
it Works
Confirmed !!
I have got my new Nook HD+ yesterday, and before I could root it, it was automatically updated to 2.0.5 by itself today.
So I did the 8 times boot manually, and the system was reset to the original firmware--2.0.4.
After the first boot by skipping the OOBE, I followed the "All-in-one" from someone0, and it works perfectly now with ADW launcher.
But I still cant get the titanium backup to run yet, it says SU error.
Thanks to someone0, leapinlar and verygreen for those great contribution :good:
haym said:
But I still cant get the titanium backup to run yet, it says SU error.
Thanks to someone0, leapinlar and verygreen for those great contribution :good:
Click to expand...
Click to collapse
You still need to run superuser once, did you do that?
Thank you for this very much. Is there no way to prevent updating to version 2.0.5 again? I came home, and my brother was playing on it, he told me something happened. I took a look, and it was updated to 2.0.5. Is there anyway to prevent it again in the future? Will the all-in-one basically disable updating? Since I did install that previously, and the version was still updated.
Sorry for the bother, and thank you very much. I will look into setting up a firewall.
Thank you again.
EDIT: I've conducted the 8-boot loop, and it should have loaded an earlier firmware; however, how would I bypass registration, or the version update check after the 8-boot loop? Thank you.
hiddenG. I had similar issue, I wanted to avoid update so I did a reset, but let it go too far and it updated me to 2005. I then did the 8 time interrupt and got back to 2004. I read here to google "nook color bypass OOTB" as the steps are the same for HD+.
It works
Only thing I'm having trouble running allinone. I don't think I'm doing it right. THe unregistered hd+ lists you as "test" and you have connectivity but no browser. I'm figuring I need to sideload a launcher and I'm looking into how to do that. I do have adb.
If you've registered you might have to reset and catch it as soon as you get to the language screen. You hold volume up. and touch lower left, then lower right to bring up "factory" screen. Then, holding vol up, touch lower right to bring up bypass OOTB.
Dave
Mine automatically updated even though I had automatic update blocked with sqlite. Furthermore, I no longer have access to content I previously purchased on that nook! I can't even download the nook app to fix, it keeps crashing when trying to sync.
Ps, if I re root using reset and skip oobe, then I still won't have access to my content, no?
Sent from my BNTV600 using xda app-developers app
I guess not, you're not registered at all.
dave
Thanks dbrons, that solved my problem. Thank you very much.
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Ferrian said:
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Click to expand...
Click to collapse
I also have the same question.
In addition, is there any way to get the "TEST's NOOK" text in the notification bar to be replaced with my own name?
someone0 said:
... unless you build your own firewall.
Click to expand...
Click to collapse
I'm actually curious if this would work. When it suddenly went into 'must get 2.05' mode and I 8-reset it, I disconnected internet right after letting it register...and it pushed me into a loop trying to check for updates and wouldn't proceed.
Any suggestions on domains to be blocked if I were to try this again?
Ferrian said:
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Click to expand...
Click to collapse
+1
And also, is there any way to get rid of the App Update notifications. There are some that I don't want to update but the notifications keep coming back after clearing them.
So pissed off now....for no reason, when booting up this time my Nook went into a boot loop and reset itself! It wiped everything from internal storage, effectively killing off hours I had spent last night getting everything set on it with apps and root. (this was all after using the All-in-one batch file which supposedly turned off automatic OTA updates)
someone0 said:
You still need to run superuser once, did you do that?
Click to expand...
Click to collapse
Yes, I did, and it works now, Thank you
I spent most the day yesterday toying with getting my Nook HD running again after the 2.0.5 update. I did find that by performing the 8 boot reset back to 2.0.0 and going through the setup process and immediately powering the HD off as soon as it began to check for updates that after I restarted the unit it would bypass the update upon powering it up again and completing the setup. After which I ran someone0's Allinone script which did give me root and load the Google market place. I was able to then load all my apps from the market and change the launcher etc.... After leaving the HD powered on and connected to the network while idle the unit did an auto OTA to 2.0.5 and rebooted on its own. Upon restart, I was at 2.0.5 and root was gone, but the update left the Google Market and all my apps and data in place. Granted I don't have root, but atleast I'm able to customize my own launcher and load and side load any apps I've see fit that dont require root.
Quote:
"I spent most the day yesterday toying with getting my Nook HD running again after the 2.0.5 update. I did find that by performing the 8 boot reset back to 2.0.0 and going through the setup process and immediately powering the HD off as soon as it began to check for updates that after I restarted the unit it would bypass the update upon powering it up again and completing the setup. After which I ran someone0's Allinone script which did give me root and load the Google market place. I was able to then load all my apps from the market and change the launcher etc.... After leaving the HD powered on and connected to the network while idle the unit did an auto OTA to 2.0.5 and rebooted on its own. Upon restart, I was at 2.0.5 and root was gone, but the update left the Google Market and all my apps and data in place. Granted I don't have root, but atleast I'm able to customize my own launcher and load and side load any apps I've see fit that dont require root."
This was the exact procedure that worked for me, other than the fact that my Nook HD+ 8 boot reset to 2.0.4. So its definitely a workable solution until the awesome devs come up with a true solution!
Sent from my BNTV600 using xda premium
can connect to pc
i got it to connect once and adb reconized it i was able to see its serial number by doing adb devices and then tries root and after the first boot my computer would not fully see it it would pop up in my computer and then dissappear it would continue to do this while i had adb enabled after i turned this off it would stop and the nook would show up in my computer but as soon as i turned adb on it would go all crazy and show and dissappear in my computer any help here would be great
Just sit tight I'm sure people are working on root for 2.0.5.
someone0 said:
Just sit tight I'm sure people are working on root for 2.0.5.
Click to expand...
Click to collapse
i have bypassed the update im on 2004
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!
Hey guys,
Hopefully someone can provide a bit of help or point me in the right direction.
Tonight I installed (what I thought was) an update but accidentally installed the original 6.0.0 image for my 6P (MDA89D).
I noticed that not much on my phone was working, discovered my error, and went ahead and updated to the latest image (MTC19X).
Most of the phone's functions remained unable to work using this image so I also tried the last image I was on before updating.
Now after trying to uninstall xposed, reinstall xposed, disable certain modules, etc I am unable to get certain functions of the phone to work.
The things I've noticed are: my recents button doesn't function, no notifications are popping up on my notification panel, I can't expand my notification panel to show quick settings, sometimes home button doesn't function at all. If it helps "vibrate on touch" was turned on for some reason after I updated the second time.
The first update I did was using FlashFire (undid xposed, installed update, reinstalled xposed), the rest of the updates were using fastboot to update everything but data.img.
Well I ended up finding the fix finally thanks to a little more googling.
running "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" and going through the setup ended up fixing it
Might as well leave this up in case anyone else needs help in the future
How to disable system update nag on rooted OnePlus 8 Pro? Thanks.
Update it.
Other than that, you can install some sort of notification blocker to remove the notification, or a magisk module to uninstall the system updater.
If you decide to update it, just let it update, but make sure that you have automatic restart disabled, and that you won't restart the phone when it says to restart. Then just go to magisk, click install to inactive slot, wait for it to finish, then restart. Voila, notification disappeared, and you still have root.
Thanks, but I don't plan to update, I have the phone set up the way I want it. Someone in another site mentioned on the Motorola Z3 he needed to freeze the OTA updater. If anyone know what the OnePlus OTA updater is called please share. These are the apps I currently have freezed.
Also how the hell did my device know there's a new version? I freezed the updaters right after root. If anyone knows the IP for the OnePlus update servers please share, I have AdAway installed, I can add them to the custom block list. Thanks.
I found out the nag is from Google Play Services so I'm SOL unless I want to de-google my phone.
Yes nagging will never stop, but your system will never be updated with the freezing. At least it is just a few times a day. I am never moving to 11 and up
awdrifter said:
How to disable system update nag on rooted OnePlus 8 Pro? Thanks.
Click to expand...
Click to collapse
remove/disable
/system/priv-app/DynamicSystemInstallationService
/system/product/app/DynamicDDSService
/system/app/OPBackup
xtcislove said:
remove/disable
/system/priv-app/DynamicSystemInstallationService
/system/product/app/DynamicDDSService
/system/app/OPBackup
Click to expand...
Click to collapse
Thanks. But I found out that the nag comes from Google Play Services, there's no way to disable it without affecting other Google apps.
raul4916 said:
Yes nagging will never stop, but your system will never be updated with the freezing. At least it is just a few times a day. I am never moving to 11 and up
Click to expand...
Click to collapse
Yes, I have came to the same conclusion as well.