My OTA updates are still showing up even though I've properly placed Fotakill.apk in the appropriate folder with the correct permissions. Has anyone had continued success with bypassing all updates?
I'm still on SuperSU version 1.24, not the later ones that allow you to still install OTAs.
UPDATE: The Surefire #1 fix in the XDA thread below did the trick:
http://forum.xda-developers.com/showthread.php?t=2209418
Some ro.build lists may not appear in your build.prop, but any variation thereof and adding and/or removing a character or two should do the trick! However, first make sure you save a backup copy of your original build.prop file in case you wish to use the OTA updates in the future!
EDIT: This seemed to only work for the OnePlus One, but not permanently for the OnePlus 3. So I just ended up freezing System Updates with Titanium Backup.
Related
Hi, I've frozen (but not removed) some bloat apps such as "My Account" and "Tethering Manager". I just want to know when an OTA is available for me to install, do I need to defrost these frozen apps before I accept the offer? Is there something else that I need to do before accepting the OTA?
defrosting before an OTA would definitely help
as it would expect some of the software to be updated already present in the system
if they are frozen, whatever it needs to be updated, might not be found, and could cause some unexpected problems
also after OTA you will most likely need to re-root the phone again, as some OTA removes the root if it needs to update the system files
AllGamer said:
defrosting before an OTA would definitely help
as it would expect some of the software to be updated already present in the system
if they are frozen, whatever it needs to be updated, might not be found, and could cause some unexpected problems
also after OTA you will most likely need to re-root the phone again, as some OTA removes the root if it needs to update the system files
Click to expand...
Click to collapse
Thanks for the answer!!
Does an OTA update completely flashes a new firmware, or does it just updates some files / install some apps / etc on the original firmware?
Also, after a OTA update, if I factory reset the phone, do I get reset to the old system, or do I get reset to the system after the update?
Sorry for these noob questions....
it depends
it will come in the form of update.zip
that the stock ROM will pick up automatically to flash, so it depends what comes packaged inside the update.zip file
I'm a bit confused by how newer versions of gapps work, as far as version numbering goes. I flashed 4.0.4 but then restored a titanium backup for all my apps and data. Can restoring backups undo updates gained from flashes like this? If so, are there cases where they won't simply re-download the newer version from the market? The fact that some gapps don't seem to have market entries is also confusing in this regard; are these programs only ever updated with android system updates? Or do they just have invisible market entries to control who can download them but still offer updates?
According to app info, my browser is on 4.0.4-257829, so I guess that's a pretty good indicator that it's the latest version. But my camera says version 1, so I'm not sure what to make of that. Is version 1 the 4.0.4 build? Has the camera app itself never been updated, but other system files add improvements as the OS gets upgraded?
JoeSyr said:
Can restoring backups undo updates gained from flashes like this?
Click to expand...
Click to collapse
Yes, restoring a backup sets everything the way it was when you made the backup - part of it's purpose is to give you a way out if an update breaks something.
If you didn't want to backgrade your apps you could try just restoring app data.
I'd have expected the apps to then be able to update through the market but I've never tried it. If they're not doing it automatically you could try opening market > my apps and seeing if it's offered there.
If it was an off market app you'd need to reinstall it manually.
Your other questions ???
Hmm, actually on looking into titanium's settings, everything that I would guess is included in the gapps bundle is set to not be part of backups (maybe it's all system apps? Not sure how much overlap between the two there is). Sure enough those apps all show as 4.0.4. So I guess by accident or design, titanium backup is safe to just run batch mode on between flashing and not have to worry about overwriting the gapps updates.
So i've made a lot of changes to stock.
1) Bootloader unlocked and TWRP recovery
2) SuperSu 1.51 installed
3) Xposed framework installed and a few modules installed
4) Changed some system apps (Deleted "Google Currents" and added "Stickmount")
I know it will be ages till 5.0 but we may see a few more OTA bugfixes till then.
So i was wondering, would any of these changes affect/break OTAs? Never taken one before tbh...
If you modify or remove any of the shipped OS files that will normally break the OTA.
If you have an extremely minor OTA, then possibly the files it patches aren't one of the ones you modified, but most of the time there are small header changes in lots of files, making it the case that effectively any file modified or changed breaking the OTA.
On the other hand, if you are just adding files (like in the case of SuperSU), then that won't break the OTA.
I cannot get my N7 to accept the 15R update. I have tried OTA, have also tried flashing the zip and sideloading the zip through ADB..always get an error that looks to be a mismatch of the hash. So ultimately I will end up wiping and re-installing...but my question is more than just that. My N7 is rooted with NRT but with no other modifications. The only reason I rooted was so that I could use Titanium backup. I hear people constantly concerned that they will lose root after an OTA update. I don't understand this because re-rooting is so easy and takes only a couple of minutes. I am much more concerned with not being able to update and having to wipe the device. This requires lots more time and effort...even getting my wireless password into the device (63 digits) takes longer than re-rooting. I have to temporarily change the password on my router to something that I can type in, then change it back after cutting and pasting in my real password, which is too long and complicated to type.
What am I missing and also, is there anything else I can do to get 15R into the device? (I have SuperSU 1.65 already.)
Thanks for helping a newbie.
Something changed after you rooted. It may not have been explicitly something you changed. It could have been one of the root apps you started using. For example stickmount will often result in the hash for debuggerd to fail.
If you post the exact error someone can probably guess what you installed that caused the hash failure. I assure you it only happens if a file was modified or deleted (unless you are one of the unfortunate with suspect eMMC memory that is corrupting on its own)
The quickest way to get JSS15R is to just use this post in JSS15R discussion thread. Use the nowipe factory option and it will preserve your data.
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
sfhub said:
Something changed after you rooted. It may not have been explicitly something you changed. It could have been one of the root apps you started using. For example stickmount will often result in the hash for debuggerd to fail.
If you post the exact error someone can probably guess what you installed that caused the hash failure. I assure you it only happens if a file was modified or deleted (unless you are one of the unfortunate with suspect eMMC memory that is corrupting on its own)
The quickest way to get JSS15R is to just use this post in JSS15R discussion thread. Use the nowipe factory option and it will preserve your data.
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Thanks for the response...I will get into that thread suggested. For the future, if an app screws things up, will uninstalling it fix things or not? You mentioned Stickmount, which I have installed. I went ahead and uninstalled it, but results are the same.
When trying to flash the 15R zip, I get:
skipping MD5 check
no MD5 file found
assert failed-apply patch check [zip name]
error executing updater binary
error installing zip
this is all while booted temporarily into TWRP....I have stock recovery on the unit.
Could freezing useless apps (some system like Google Books and useless keyboards) with Titanium Backup cause the update to fail? I tried unfreezing everything that I had done...still no luck. I'm just trying to get a feel for what to do and not do in the future...
Thanks much!!
OK...followed your thread ...read everything and since I saw an error about debuggered somewhere on my N7, I used your debuggered update, flashed it with TWRP and then was successful in flashing the 15R update.zip. So it must have been as you said...Stickmount was the problem and it messed up the debuggered file. I'm still wondering if freezing apps with Titanium backup will mess up an update or if I did not need to defrost everything before trying to flash the zip???
Thanks so much for the help...another success story and noob learning more and more about what the heck is going on in Android.
CCT1 said:
I'm still wondering if freezing apps with Titanium backup will mess up an update or if I did not need to defrost everything before trying to flash the zip???
Click to expand...
Click to collapse
It has nothing to do with freezing apps. Freezing apps won't have any negative effects on your ability to use an OTA successfully.
Stickmount backs up debuggerd, makes some changes to it, then restores the backup, but sometimes it gets out of sync. When it gets out of sync, your original debuggerd is lost even though there is a backup file because the backup is of the wrong file.
Uninstalling stickmount wouldn't have fixed this issue because it already made the modification to debuggerd.
Keep in mind, normally it isn't root that causes the OTA to fail. It is the use of those capabilities root gave you, to modify or remove files, either directly or indirectly through a 3rd-party app that causes the OTA to fail.
Gotcha...thanks for the help...your debuggerd script fixed everything...I've put it away for possible future use. Titanium Backup and Stickmount are the only apps I have that require root...I will keep this in mind. To a lesser but similar extent than in Windows, I like to keep a system lean and mean....I think Android can benefit from this also.
Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
UPDATE: DO NOT install the update if you don't have stock recovery. You will end up in a boot loop.
Sent from my LG-D851 using XDA Free mobile app
Lol I just created a thread myself! I am rooted and custom rom so I am totally waiting.
i just got it too, it said android update but I'm not entirely sure what it's for
InsaneJester17 said:
Is anyone else getting prompted for a system update? I'm rooted so I don't want to install. Update is 154.6 MB.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I also did, I am on sky rom and it probably won't work, but I don't want to try to install it.
Well its quite a small update at 154 mb
Installed update
Hey guys I just installed the update and it broke my root :cyclops:
Were you able to root again?
Apparently it's D85110m update. So it's updating from D85110c to m. The person that I saw that updated hadn't rooted so no clue on the rooting thing.
Count me in the group with system update notification. I got rid of it by installing xposed module GravityBox, going under status bar settings - ongoing notification blocker - Google Play services (picture looks like that of update) - reboot.
I don't know what other notifications this may block, but for now, it gets rid of that. Also of note, I would NOT take the OTA. Usually it breaks root and/or bootloops you.
HELP
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?
zcgofaster said:
Were you able to root again?
Click to expand...
Click to collapse
I haven't tried to re-root yet. I was rooted with stump root earlier. Stump root doesn't work again because it thinks that my phone is already rooted. I'm going to do some light battery tests before trying to root again, this time with purple drake.
Maybe i might restore the slimkat alpha and hide there until this gets sorted out
I decided not to update to fear my bootloader/root so I tried to extract this with file manager and kept crashing. I can only post the name of the file but above users are correct contains 10m from 10c hopefully devs can find out exactly what's in the update. b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip
thiefinthenight said:
So in my half awake brilliance, I installed the update. My phone is now boot cycling to the TWRP recovery. Any ideas?
Click to expand...
Click to collapse
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667
Wonder if i could do a restore and keep wifi off so it won't download
hawkstwelve said:
I would try and follow this guide:
http://forum.xda-developers.com/showthread.php?t=2818667
Click to expand...
Click to collapse
Will this reset the phone? Will I lose all data?
thiefinthenight said:
Will this reset the phone? Will I lose all data?
Click to expand...
Click to collapse
I believe so yes. But if you are truly bootlooping, I don't believe you have many (if any) other choices than wiping clean and starting fresh.
I'm all stock so I upgraded.
It is in fact D85110m
I've only had it up and running for a few minutes and I already noticed two things.
- There is a slider feature added to the lock screen to instantly open the camera.
- I didn't think the phone was sluggish or laggy out of the box but I immediately could tell it runs smoother now with transitions between screens/apps. e.g. There used to be a bit of lag when opening the Recent Apps. Not anymore.
We'll see how it goes.
The IR blaster works better for me now. I guess the update made it more powerful somehow.
if you have twrp installed or have modified /system you should not take this OTA. if on twrp things will get weird(as evidenced above..) and if removing/modding any default files in /system the zip will most likely fail.. as it checks for all original files first before the OTA update gets patched in.
as for the twrp issue.. I can only assume that it's due to the update/phone expecting stock recovery... and not getting it. there are flags set in the phone that tell the phone what mode to boot into... since you dont have stock recovery the phone is confused. check out this thread - http://forum.xda-developers.com/showthread.php?t=2451696
the fota and misc partitions are tied to this... try to zero out fota first. if that alone doesnt let you out of twrp... you may need to wipe misc. be sure to backup any partition to computer(dont just save on phone sdcard.. never know when it could get wiped..) before erasing anything.
as for this update(10m)... anyone taking it should be careful that the bootloader/downgrades have not been locked/blocked. I'll be waiting for others to take that risk first before even considering taking the ota.
*update* can confirm update is safe.. bootloader is not locked.. still rootable.
as for root... I doubt purple drake is blocked.. but is possible. I'm very sure Stump is still available as an option(tho app may need update).
if you got the update and dont want to take it.. and want the notification gone you should be able to use a file explorer to delete the update zip from the the /cache directory... as well as rename the LGFOTA.apk file in /system to LGFOTA.apk.bak.
I can also confirm that disabling OTA updates in the hidden menu works. the moment I set it back to "on" (i set mine to off day 1) and rebooted the update came in.
d851 hidden menu > wlan test > ota setting > off > reboot (if you have been notified of an available update do NOT reboot until you have deleted the ota zip first)