Hi,
I wanted to update my phone to the new 45.4.13(?) update but it keeps giving me errors since I uninstalled some of the stock apps that were useless (for example, AdService.apk). Is there a way to either mount a partition that has the factory setting stuff, or modify the update to not check the hashes of the stock apps I don't have, and if I can do the latter, would that break the update/my phone?
Also I want to hear if anyone has updated their thing to 2.3.5 after superuser released their ota survival, and did that work?
-BananasGoMoo
Related
I recently just got a Neo V from a network provider without a plan. When I installed PC companion and plug it in, it prompts for a firmware update and I did. After that, the rubbish apps of the provider still remains.
Recently I unlocked bootloader (SETool?), fastboot into CWM, and adb pushed Superuser.apk and su (by myself), and it is rooted.
So with these two events, a question comes in my mind: How does official firmware update work? Does it 1) flash the system partition, 2) replace files only, or 3) by other methods?
I was thinking that if it was 1, those rubbish apps should have been removed and if I update again it would be unrooted. But if it was 2, wouldn't it be either more difficult to update or less useful?
It flashes the firmware to the system partition, but they check which firmware you currently have, and download the same firmware version with the same bloatware.
You can remove the bloatware with rom toolbox it's the easiest way
For me, it totally replaces system partition, but leaves untouched user partition. My phone was be rooted too, some bloatware removed and some programs moved to ROM. After update, blootware was be restored and programs, moved to ROM, deleted!
Well I understand apps under data is preserved and they can be uninstalled using default Settings UI.
So rom update is region-specific?
These apps (bloatwares):
$ ls /system/app/*_
/system/app/com.game.crazyfarm.apk_
/system/app/com.kaixin001.activity.apk_
/system/app/com.kobobooks.android.apk_
/system/app/com.mas.apk_
/system/app/com.skysoft.kkbox.android.apk_
/system/app/com.sonyericsson.androidapp.lunarcalendar.apk_
/system/app/skyphoto.hk.shotnprint.apk_
I added an underscore to prevent them from being displayed, so they actually exists in firmware update?
I have the opposite problem to many of you guys. Original 16g Nook Tablet running stock 1.4.0, rooted the week I bought it back in Nov '11. I've (successfully) blocked OTA updates since then using a multitude of methods including the registry hack (change from auto to manual, change version number to 9.9.9) plus I played around with the NT Hidden Settings app and disabled OTA updates from there also.
Now I actually want to update to 1.4.3 since it's the end of the line final update to NT, and I can't seem to make it happen. I downloaded the ZIP file from B&N support page and put it where the instructions said (top level directory as visible from computer via USB). I reverted my registry hacks correctly I assume as it didn't cause brick or bootloop problems. I also reverted the NT Hidden Settings OTA block.
I know it needs to sleep for awhile before it loads the update, but it had a nice sleep overnight and I'm still on 1.4.0 and still have root. Is it possible to flash the update via recovery from the SD card? Any other way to force the update? Does it need to be renamed from nooktablet_1_4_3_update.zip to ACCLAIM_UPDATE.ZIP or something like that?
http://www.blog.totaltech101.com/repartitioning-your-16-gb-nook-tablet/
If you want repartition and going back to 1.42 then use that.
Sent from my DROID RAZR using Tapatalk 2
cellhead said:
I have the opposite problem to many of you guys. Original 16g Nook Tablet running stock 1.4.0, rooted the week I bought it back in Nov '11. I've (successfully) blocked OTA updates since then using a multitude of methods including the registry hack (change from auto to manual, change version number to 9.9.9) plus I played around with the NT Hidden Settings app and disabled OTA updates from there also.
Now I actually want to update to 1.4.3 since it's the end of the line final update to NT, and I can't seem to make it happen. I downloaded the ZIP file from B&N support page and put it where the instructions said (top level directory as visible from computer via USB). I reverted my registry hacks correctly I assume as it didn't cause brick or bootloop problems. I also reverted the NT Hidden Settings OTA block.
I know it needs to sleep for awhile before it loads the update, but it had a nice sleep overnight and I'm still on 1.4.0 and still have root. Is it possible to flash the update via recovery from the SD card? Any other way to force the update? Does it need to be renamed from nooktablet_1_4_3_update.zip to ACCLAIM_UPDATE.ZIP or something like that?
Click to expand...
Click to collapse
If you rooted your tablet you don't need to update to 1.4.3. No difference if you're using go launcher as your main screen.
cellhead said:
...
Is it possible to flash the update via recovery from the SD card? Any other way to force the update? Does it need to be renamed from nooktablet_1_4_3_update.zip to ACCLAIM_UPDATE.ZIP or something like that?
Click to expand...
Click to collapse
nooktablet_1_4_3_update.zip in original form cannot be installed with non-stock recovery programs such as CWM or TWRP. The various "Restore to Stock 1.4.2" methods/tools make use of a version of the stock 1.4.2 update.zip that was specially "repackaged" so as to be flash-able by these tools.
Perhaps you should consider a two-step process: first restore your NT to stock 1.4.2 using one of the "Restore to Stock 1.4.2" methods/tools (e.g., flash_stock_1.4.2.zip at https://github.com/succulent/acclaim_recovery_sdcard), then upgrade to 1.4.3 using BN's regular upgrade process.
You might also want to take a look at this thread http://forum.xda-developers.com/showthread.php?t=1420408.
Has anyone been able to successfully disable the system update notification on the watch for the 5.0.2 update yet? If so, would you mind sharing your technique and what is required (root, adb, etc...) I've not yet rooted but unlocked my bootloader and have installed Arter97's 2.1 Kernel. I toyed around with the idea of trying to rename or delete the update.zip in the /cache partition, but I apparently have insufficient permissions via adb to that partition, probably due to not rooting. If I simply deleted the update.zip, I expect that it will simply download again and I'll have this same issue again right? Thanks all.
Nobody has figured this out? I just don't to update; seems like more problems that I don't want.
altivoid said:
Nobody has figured this out? I just don't to update; seems like more problems that I don't want.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=59230170
I'm trying to brainstorm what is the easiest way to install, on a not-so-techy friend's phone, privacy related root-access apps such as AFWall firewall, or even Xposed framework
and still have the phone able to function normally e.g. install OTA updates automatically without going into recovery, flashing, adb, any other advanced "crap" to re-root.
Is there any way to, not necessarily root the OS, but somehow inject a root app into a phone, ONCE, and then never have to worry about it with OTA updates?
Possibly:
- extract the ROM from the phone, make modifications so some part of it that doesn't get overwritten by the OTA updates?
- install a custom android ROM like a lineageOS which somehow has root but also OTA updates? (does this exist?)
Cheers
There was also at one point a root app that claimed it can update your phone and re-root but can't find it anymore. Is there really no way to make this process less involved? Or, again, to inject what you want once and never loose it.
so I picked up a used pixel from craigslist. seems ok. but I starting thinking... how can I be certain this phone is not booby trapped. it would be awful to have a trojaned device and not really know it.
I searched quite a bit about about malware that can survive factory reset. so it seems that simply resetting is not so great.
then I thought adb sideload an official google factory image to both slot a and slot b would purge any demons. but then again, I cannot find any documentation that make it clear what get overwritten and and what doesn't. (eg do the bootloader or recovery partition remain intact... seems like a great place to hide malware on a booby trapped phone). similarly, it is unclear what /system paritition blocks get replace.. all of them? some of them? can a clever trojan/rat survive an ota?
and then there is the full factory image install via fastboot. the problem is that I cannot enable oem unlocking b/c Verizon locked bootloader. booooooo
final thing. and the trigger that really had me thinking about this. after setting up the phone and connecting to the network, I saw a notification that subtley asked to install a Google screen reader. no idea why. and no google searches return anything useful. was this device hacked already??!
specifically the notification said:
"install app for screen share" and "tap to install from the play store"
so, any security minded android users out there who can help me understand if I need to trash this phone?
Infrequent pop-ups when using a web browser or when running an app can be normal. However, if you are getting pop-ups even when you’re not opening a browser or when using a totally different app, there could be malware in your phone. Malicious pop-ups are often brought about by a bad app that you may have installed in the past. In some cases, legit looking apps may update to a sinister version after some time and cause pop-ups to be displayed.
Run the phone in safe mode and observe it. Safe mode is great tool in detecting a problem app. On this mode, all third party apps will be suspended so if the problem is absent when your Android is running on safe mode, that means there’s a malicious app in the system. While in this mode, you should be able to use preinstalled apps normally as well as use basic networking services without a problem.
My recommendation to have a malware-free phone:
Do a factory reset
Before re-installing any app install an anti-virus app
So will sideloading an official factory OTA image using adb from recovery, completely remove any malware? (I read about malware that can survive a factory reset.)
Also, has anyone else ever seen a notification asking to install a screen reader? This appeared after a factory reset, immediately after connecting to the wifi network. No apps installed.
A factory reset really only deals with the Data and the Cache partitions. System partition isn't affected. This is true regardless device is rooted or not So if malware got installed in System partition it survives a factory reset. A factory reset will also not remove any ROM upgrades or OTA's.
Hopefully by now you have a better understanding of what a factory reset is.
May be the browser - what typically is installed as system app / system-privileged app - is the culprit: Use another browser and see what happens.
I think I understand how the factory reset works. For this discussion, I am do used on Google Pixel line, no modifications, and no root, and only app from the official Play Store.
The adb sideload of a Google factory OTA is the part I don't fully understand.
For example, doe the OTA merely replace files? Or does to do a bitwise blocklevel swap? Does it modify anything in the bootloader, or recovery partitions?
I cannot find clear documentation on this.
The notification requests to install Screen Reader do not come from Chrome or any browser. They appear to come from the system. (Android 10).
So what I am trying to figure out is whether some malicious actor/app installed a persistent malware into the system partition, or the bootloader, or the recovery. Such that a factory reset cannot remove it (like with xHelper malware)
Like for example, can a malware get into the system partition, and a manual adb OTA sideload , or even manual fastboot factory image install, fail to remove the malware from the system partition? That would be. a nightmare for security.
Finally, I cannot find any documentation from Google that Pixel (3) on Android 10 will automatically try to install a screen reader as a native operation.
Basically, is this used, never rooted phone, permanently Trojan-ed junk now?
@thehighhat
Sorry to say this: I'll no longer waste my time with this ...
oops: duplicated post deleted
jwoegerbauer said:
...
My recommendation to have a malware-free phone:
Do a factory reset
Before re-installing any app install an anti-virus app
Click to expand...
Click to collapse
OK. Not sure why you're done with this - if you have insight, sharing it is good for everyone.
anti-virus (13 different ones) all show no malware. shows it is clean.
there are well known malware that can survive a factory reset.
the notification to install "screen reader" occurred immediately after a newly wiped phone connected to internet, even before any of the default apps (chrome, settings, etc.) opened
still looking for answers from someone who knows:
has anyone ever seen a system notification asking to install a "screen reader"?
does anyone know if
Code:
adb sideload official.google.ota.img
on a pixel modifies the boot partition or the recovery partition?
does anyone know if that manual ota install will guarantees the system partition contains only unmodified valid files/blocks?
thehighhat said:
OK. Not sure why you're done with this - if you have insight, sharing it is good for everyone.
anti-virus (13 different ones) all show no malware. shows it is clean.
there are well known malware that can survive a factory reset.
the notification to install "screen reader" occurred immediately after a newly wiped phone connected to internet, even before any of the default apps (chrome, settings, etc.) opened
still looking for answers from someone who knows:
has anyone ever seen a system notification asking to install a "screen reader"?
does anyone know if
Code:
adb sideload official.google.ota.img
on a pixel modifies the boot partition or the recovery partition?
does anyone know if that manual ota install will guarantees the system partition contains only unmodified valid files/blocks?
Click to expand...
Click to collapse
If you fastboot flash an official google system.img partition. From Google. With the correct hash value to insure correct download. It should flash the entire partition. Same goes for any other partition. If you have a certified unmodified image and flash it, the entire partition should be flashed, not just part of it.
With OTA updates. You only get patches. At least that's how the normal process goes. You got the smaller sized ota update and it only modifies the specific files that are being patched for that particular OTA update.
So with normal OTA only pieces of the partitions get updated. Sometimes they all are not touched with every update.
Delgoth said:
If you fastboot flash an official google system.img partition. From Google. With the correct hash value to insure correct download. It should flash the entire partition. Same goes for any other partition. If you have a certified unmodified image and flash it, the entire partition should be flashed, not just part of it.
With OTA updates. You only get patches. At least that's how the normal process goes. You got the smaller sized ota update and it only modifies the specific files that are being patched for that particular OTA update.
So with normal OTA only pieces of the partitions get updated. Sometimes they all are not touched with every update.
Click to expand...
Click to collapse
Thank you. This is exactly what I was looking for
So it sounds like file level replacement instead of block level.
Does the ota verify the other files on the system partition that it does not intend to modify?
thehighhat said:
Thank you. This is exactly what I was looking for
So it sounds like file level replacement instead of block level.
Does the ota verify the other files on the system partition that it does not intend to modify?
Click to expand...
Click to collapse
It does in the sense that it verifies before and after the process begins/ends, the correct size of the partition. This is true in the sense of Ssmsung devices and how the typical standard recovery image works.
But it is the update zip that does most if not all of the size/digest verifications after the files have been patched. Because there is no real way for the rom to know how big the updated build(s) is going to be before the update arrives.
Generally I've seen it verify all the hash values are the same as last time it updated when it begins. And the update zip specifies the ending size.