Hello,
this is my first post.
My D6503's Camera stopped working after I updated to MM, well only after I played around with the permissions for the google services app. My phone was running stock and I didn't think that anything serious would happen.
I denied the google services permission to my camera in order to cut down on its power usage, unfortunately my camera and torch is now unable to open and keeps saying that the camera is unavailable.
I've tried various third party apps, when I launch them they say the camera is in use.
I've also noticed that my battery life has severely decreased as the camera itself is warm and I think it doesn't shut off.
Since then I've reset the permissions, factory reset, wiped the caches (including the dalvik) various times, rooted and installed a recovery and wiped everything, I've flashed every conceivable stock rom and currently I'm running a custom rom for a locked bootloader.
A few things that I've been wondering:
1.) Is it possible to reinstall or flash the hardware drivers specifically for the phone?
2.) Might I be able to fix this problem by unlocking my bootloader and installing a custom kernel and then reverting back to stock and restoring the TA partition?
3.) is it possible to totally wipe the phone's partition and install everything from scratch?
4.) The sony android system used to have a browser app that is now disabled and replaced by chrome, I've noticed that the browser app is actually still available in the software but a setting somewhere is specifically blocking the use for it. Might there be a service setting that I could reset to gain the function of my camera again?
5.) Might my TA partition settings be influencing my camera somehow (maybe after being corrupted) and is there a way that I could change the settings or edit my TA partition?
Related
I've been getting systematic breakdown of my device whereby processes and apps will suddenly for no reason on their own be forced to stopped unexpectedly. So for example Google Framework, gapps, acore, play store then apps will be unable to start and force close immediately e.g. swype, titanium backup etc etc. Now this has happened on many different ROMs e.g. DSC, Longhorn, PCM7, Mokee and now even on the AOPK CM9. So it isn't down to a particular ROM as they always flash fine and my device runs fine otherwise.
A complete data wipe and re-flashing of a ROM always restores the phone to "normal" but I fear my device is dying. Has this happened to anyone else?
try installing different launcher...
Really? Why should that make a difference? They mostly have different launchers though.
It doesn't.
Does it do this without any of your apps added?
SuperKeeper said:
I've been getting systematic breakdown of my device whereby processes and apps will suddenly for no reason on their own be forced to stopped unexpectedly. So for example Google Framework, gapps, acore, play store then apps will be unable to start and force close immediately e.g. swype, titanium backup etc etc. Now this has happened on many different ROMs e.g. DSC, Longhorn, PCM7, Mokee and now even on the AOPK CM9. So it isn't down to a particular ROM as they always flash fine and my device runs fine otherwise.
A complete data wipe and re-flashing of a ROM always restores the phone to "normal" but I fear my device is dying. Has this happened to anyone else?
Click to expand...
Click to collapse
+1 sounds so familiar its spooky.
Strephon Alkhalikoi said:
It doesn't.
Does it do this without any of your apps added?
Click to expand...
Click to collapse
Well it's very hard to say that because it generally progresses in how bad it gets. I've had ROMs working fine for a week or so before they give up the ghost. I'd be inclined to say it maybe a dodgy app but I've had a huge range of different apps because my knowledge and ability with Android has come on since I first started with custom ROMs.
Bump.
After reboots, I lose data of all my apps so they're like they've just been installed, e.g. Whatsapp asking to verify my number etc. Also after a reboot none of my installed apps are in the launcher but in the settings they are listed under their process name (e.g. com.adobe.flashplayer) with a grey SD icon next to them. Multiple reboots and wiping of Dalvik haven't fixed this. So I really don't want to wipe data but looks like I will have to.
Furthermore, an app can be "restored" simply by re-installing it, the device says that I am replacing an already installed application.
This is a huge problem because the pins in the device's port are bent so I have to charge batteries externally.
I'd spend a little bit of time and attempt to straighten out those pins, as it will help. However, while I do believe wiping data at the very least is in order, I'd be more inclined to go with the full factory reset and start over.
Yeah always happen to me too..
Can you try to check via Recovery Mode and see if Cache partition is OK?
Because I always get that error if Cache partition (innersd5) crashed..
and to fix that I must disassemble DS and takeout the internal SD card and mount it to PC..
Then you can format the Cache partition to ext3 (the partition is small size around 230MB)
Hope this help you
Hi,
I have some really strange App crashes since a few weeks: Google Photos won't run, an app from my carrier (MeinVodafone) and Google Search. The strangest thing is that Google Search is working...partially. I can not open the app directly, but I can open it via voice (timer etc is working and search also has no problems) and I can open the settings in Google Settings (Play Services). Attached are some catlog logs.
I'm running ParanoidAndroid 5.1 (5.1.1) on an d802. Build is from 1st june.
I'm also running XPosed Framework. I already thougt that WebViewGoogle could be the cause for that, but that would affect more apps and I haven't found any hint on that in the logs.
Any tips what could cause these strange crashes?
UPDATE: I just changed my system language to english (from German) and at least Photos is running without problems...
I have 3 possible solutions..
1. Reinstall apps
2. Wipe /data, /cache from recovery
3. Reinstall the rom or choose another rom.
Third should work but idk if you want that.
I already reinstalled them and I'm already running the second or third update. I'll try it with wiping /cache and /dalvik-cache, /data would delete all apps
Ok please update the thread with news
It looks like I cannot wipe /cache, it says done but shows the old "E: cannot mount storage" and then I stuck on boot animation for over 15 minutes, way longer than normal. Repair it also doesn't help that.
I know I can delete dalvik-cache by deleting the files in /data/dalvik-cache/arm. Is there a way for cache too? That would be the only way to do that
@Artim_96 yes there is a way but I think its pointless. Try flashing stock rom or any other non-lollipop rom and then return to lollipop.
I don't think that's the only possible solution. I'm on PA since January, the bug with Google Search and MeinVodafone is only since a few weeks.
It surely isn't only possible solution but it is recommended.
it is pointless to flash a KK ROM, restore the apps, install an LP ROM and restore the apps again. It just makes no sense to do so.
I never said to restore apps, wipe everything (system,data,cache) and flash rom and gapps.
So you want me to reinstall everything, right? Are you kidding me? And what should I use? A blank system just with Google Apps?
I now got search to work again, the problem was the XPosed Module "Force Immersive mode", the other app is still not working, so I made another log with all modules disabled.
But I found another bug: the location service seems to be not working properly: no app that should be shown is there and Google Fit was not working today. (I never really use it, so I just saw that and because Fit was draining the battery to much I just reinstalled it to test it)
Sony Xperia SP C5306
Jellybean 4.1.2
Rooted
I'm having an issue, wherein the stock browser uninstalls itself on every boot.
The .apk is still in the 'system/app' folder but the icon is gone from the app list, and when I try to open a link, I'm told there is no application with which to perform the task.
I've deleted the app and it's .odex file, as well as the data in 'data/data' etc, and reinstalled it both manually as well as with Titanium Backup.
It works fine, (using it now in fact), but upon rebooting, it's gone again.
The only thing that has significantly changed prior to this was the installation of 'Cydia Backport'.
After uninstalling 'Cydia', I lost the browser.
I reinstalled 'Backport', hoping to regain functionality, but the issue persists.
Also, when I boot into TWRP and attempt to backup or restore, I'm informed that it was unable to 'unmount' the system.
This behavior did not pre-exist 'Cydia' either.
'Cydia Backport', is intended to insert recent Android security updates, into older OS's.
Any ideas, folks?
Is there a command somewhere in the boot script that could be doing this?
If so... Can I edit it?
I, have emulators and editors available, I just can't find the 'uninstall your browser every boot', command.
Is boot logging available somehow so I can see where the command initiates?
:-S
Solved!!!
As per usual, I slashed and burned, and raped and pillaged, and after a harrowing fight with the demon, I once again have full control of my browser (post boot), and 'Cydia' is a thing of the past. No thanks to Avast, and Malwearbytes - neither of which detected significant changes to the OS.
Why doesn't Android have an equivalent of Windows SFC???
I rooted my S9+ following this thread:
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974
Since I tempered with some files in the folders data & android and a few others the root access for the modded camera app from zeroprobe says: „check root access“ and it won’t work properly.
In twrp boot mode, I tried wiping and all the apps I previously installed were gone, but upon reinstallation of said modding app the problem remains.
Is there a specific folder I should wipe or how would I go about starting from scratch?
And no, I didn't take a backup yet... (at least not on this phone, but on a second S9+, could I use that one?)
got it working again. As so often when assuming something, the problem was apparently not that I copied some files around. It seems that I needed to start magisk at least once. After that it worked. The modding differs slightly, maybe due to an update of the app. Just guessing here, but at least i got it working.
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.