Related
I hope this hasn't been covered here before. I've searched all over xda and Google for a solution but no one seems to address my specific situation.
I used to have a Samsung Epic. I traded my friend for an evo. I swapped our SD cards since epic comes with 16gb. When I got the phone she hadn't made any modifications. Completely stock. My accelerometer and notification light worked fine at the start. Since then I've rooted and installed many custom roms. Before I traded her the epic I was trying to create more space on my SD card and wiped the whole thing. Bad idea. The Rom I was using kept force closing closing all my apps. I flashed a backup I had stored on ny computer and it was no problem.
I'm not sure when my accel and LED stopped working with my evo..these aren't features I use or pay attention to on a daily basis. I only really care about the accel and have been trying to fix it for quite a while now.
I've read in different threads to A) Unroot, wipe everything, and use an RUU to go completely back to stock. B) download and push the accel file over the old one under data/misc in the root of your SD and C) download the sensor debug app to see if it gets a reading. Ive tried them all. I'm back at stock, unrooted. I downloaded the file but when I wiped the SD card it deleted all of my root folders. When I used the RUU it created some of the original folders but not all of them and not the ones specified to replace the files. I tried to create them myself but it made no difference. When I opened the sensor debug app it did not get a reading..or...at least I don't think so, but I don't know exactly what is supposed to come up.
Everything I've read so far tells me this is a hardware issue...but if it was working when I first got it how could it be an issue with the hardware? I had to have erased some necessary file or source that's causing this problem. Right?
Does anyone have any thoughts or ideas? I guess since I'm not rooted anymore I could go to Sprint and have them replace it but I don't really feel right about doing that and honestly id rather just learn what I did wrong and how to fix it. I feel like there's got to be a way to format my SD card to the evo stock settings.
My only thoughts would be to either copy the contents of the original owners SD card, unless theepic has already gotten rid of her original evo files, or copy the contents of someone else's SD card who's evo still has these things working. Would that work?
Thanks in advance for reading this novel and for any input you might have. I've been lurking about in these forums for a few months now and there are some brilliant devs and posters around here.
Oh. One more thing. As I mentioned earlier, the accellorometer is what Im really worried about fixing. The notification light is of little importance but I feel confident that these two issues go hand in hand.
Thanks again for anything you may be able to contribute. This is a long long post for something noooot really that important or common.
I know it's early on but I rooted my Samsung galaxy tab 8.4 and I am trying to do a backup of my apps and I cant do a backup to my external sd card. TB is saying it isn't writeable. I have used the back button and such to manually change the directory. I'm familiar with doing that. I can backup to internal storage but obviously I don't want to waste the space when I have a 64gb micro sd card. Thanks for the help.
bckrupps said:
I know it's early on but I rooted my Samsung galaxy tab 8.4 and I am trying to do a backup of my apps and I cant do a backup to my external sd card. TB is saying it isn't writeable. I have used the back button and such to manually change the directory. I'm familiar with doing that. I can backup to internal storage but obviously I don't want to waste the space when I have a 64gb micro sd card. Thanks for the help.
Click to expand...
Click to collapse
I can confirm the same issue. I've verified that the root directory is set to R/W using "Root Explorer" from the play store. For some reason, I can't get TB to see it as R/W, though.
Saving other items to the external card seems to work just fine. Camera saves there, no issues. Weird.
leatherneck6017 said:
I can confirm the same issue. I've verified that the root directory is set to R/W using "Root Explorer" from the play store. For some reason, I can't get TB to see it as R/W, though.
Saving other items to the external card seems to work just fine. Camera saves there, no issues. Weird.
Click to expand...
Click to collapse
It will get figured out soon enough. im just happy to be able to do a titanium backup. Lots of work installing stuff
I couldn't even create a Nova backup to the external SD card
Sent from my SM-T320 using Tapatalk
CAR1977 said:
I couldn't even create a Nova backup to the external SD card
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
It is a 4.4 permissions issue. I found a possible fix if it works I will post it.
This worked for me. You have to be rooted to do it though.
http://forum.xda-developers.com/showthread.php?t=2617921
nrage23 said:
It is a 4.4 permissions issue. I found a possible fix if it works I will post it.
This worked for me. You have to be rooted to do it though.
http://forum.xda-developers.com/showthread.php?t=2617921
Click to expand...
Click to collapse
Confirmed, this works. Nice find!
Where did you find root?
Sent from my GT-I9505 using XDA Premium 4 mobile app
uberboyd said:
Where did you find root?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Root was achieved yesterday. CF Auto Root
i am rooted and using es file explorer. when i try to save it a box keeps coming up saying an error occurred cannot save.
got it. have to mount the system.
bckrupps said:
i am rooted and using es file explorer. when i try to save it a box keeps coming up saying an error occurred cannot save.
got it. have to mount the system.
Click to expand...
Click to collapse
Root explorer works much better for modifying root directory the ES does.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
Root explorer works much better for modifying root directory the ES does.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
Yea thats what i figured out. So nice to be able to back up to the sd card and the process literally took a minute. Cool find.
I was able to fix this issue by simply installing Folder Mount. When you first open folder mount will offer to repair this permission issue for you. I said yes and it worked. Folder mount also stated this is specific to Sammy 4.4 roms... Just an FYI. Thought I would share.
Sent from my SM-T320 using Tapatalk
Unfortunately, it's not something that Samsung decided to do, it's something Google started back in Android 3.2 and is now apparently asking OEMs to follow their lead on - or else the OEMs aren't reading the codebase much, which I think is also a problem.
The external storage permssions were spotted and commented on by Chainfire (he who gave us root, hallowed be his name ) in 2012!
https://www.xda-developers.com/andr...-preventing-write-access-to-external-storage/
http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
I'm not 100% on this, but I think that the Samsungs are one of the first sets of devices to get KitKat and to have sdcards. (don't know what the status of the gpad 8.3 is) It will be interesting to see if the Gpad 8.3 does the same thing; I'm pretty sure the Tegra Note did, and then EVGA pulled back on their KitKat update due to bugs, of which this was one (glad they called it a bug, but if they'd looked at the code before implementing the changes...)
This issue goes way beyond the sdcard. Remember when your device could be connected to your computer and turn up as a mass storage device, not a media player or a camera?
The MTP protocol originally implemented by Google was hugely troublesome on that score when it was first introduced. There were absolutely insane failure modes. To get an accurate readout of what was on your device you couldn't disconnect from your computer and reconnect, you couldn't disconnect, reboot the Android device and reconnect - nope, you had to reboot your computer.
I haven't thoroughly tested failure modes but at least the warning on copy from PC to Android works correctly now.
When first implemented by Google, file deletions on in Android were not reported to the computer connected to it if they occurred while connected. So you could move a folder and then try to copy files that didn't exist, and Android wouldn't report the file was not there.
This is an example of silent failure, which is the worst possible failure mode. It gets beaten into the heads (or once did) of programmers that you always produce and report an exception on failure. Not doing so is negligent and might be actionable depending on the context.
I just deleted a file from the Samsung and it's taken more than 30 seconds for the Windows system to get information on what's on the Samsung.
Great - I also couldn't enumerate my local disk drives while I waited, more than 3 minutes (i7-2600k, 8 G ram - not a PC side issue!) I finally disconnected and reconnected the USB cable and was able to get my disks to populate immediately on disconnect, and an accurate poll from the Samsung on reconnect.
I suspect that Google's 'fix' for the not-notifying-on-delete bug is to throw a disk not ready message back at the host system.
So, why does Google not see any of the following as important?
- easy local disk mounting
- viable sdcard use
- well-written MTP implementation
I don't think it's about the cash - sure, Google's selling a few books and a few movies and such, but they're really an advertising broker; the revenue from that isn't why they're worth gazillions.
I think it's actually much more insane than that: Google is all about big data and the supremacy of databases over all else.
Including files themselves - Google wants to drive toward a world where files don't exist, only pointers in databases exist.
http://glasskeys.com/2011/02/28/why-google-uses-mtp-instead-of-usb-file-transfer-on-android-3/
is a perspective on MTP that is essentially diametrically opposed to mine - it's quoting Google as pointing out that there is both simplicity and allegedly a greater degree of security from MTP.
The security comes from the filesystem retaining 'nix style ACLs and helping to maintain sandboxing between applications by not exposing storage as a fat32 filesystem and thereby giving up granular access controls.
---------
(As an example of silent failure that I think may be the subject of civil litigation: the flaw that broke SSL/TLS validation on most Apple devices - phones, tablets and OS X based computers. If you look at the code, it's blindingly clear what happened.
http://appleinsider.com/articles/14...pdate-is-present-in-os-x-fix-coming-very-soon
http://arstechnica.com/security/201...aw-in-ios-may-also-affect-fully-patched-macs/
This flaw may well explain the Snowden documents that indicate that the NSA has access to any Apple device at will. When those documents were first being reviewed, there were two responses:
- it isn't true
- Apple is in bed with the NSA.
Ignoring a bug that easy to spot in a functional test for years tends to make me wonder if the second explanation may not hold water.)
Hopefully this can help someone. I couldn't edit my *.xml file even though I am ROOTED. But I found this:
https://play.google.com/store/apps/details?id=nextapp.sdfix
and it worked!! Now Titanium Backup is able to write successfully to my sdcard.
The app works great. I would recommend it for anyone on 4.4
Sent from my SM-T320 using XDA Premium HD app
PRESOLVED: My Tab is possessed by the devil!
When I tried to write a file to my Galaxy Tab Pro 8.4's external SD card with Astro and it wouldn't work I was flustered. A little research turned up the crippled SD support in KitKat and how to fix things with the simple platform.xml hack. I did that, and all was right with the world again.
Then I got another 8.4, and actually cloned the first one to the second one with a nandroid backup. I also moved my SD card from the first to the second. Eventually I sold the first one and am just left with the second one. But somewhere along the way I lost the ability to write to the SD card, and I can't get it back!
The hacked platform.xml file was of course cloned along with everything else, but it just doesn't work. What's just as bad, or worse, is that apps which should write to external SD even without the hack (and which did, prior to this issue developing), such as Samsung's My Files, and Root Explorer, also are no longer able to!!!!
So to try and fix things, I flashed this ROM to my Tab: http://forum.xda-developers.com/showthread.php?t=2698460 But I still can't write to external SD, even with My Files!
Here's another problem, which may or may not be related: I also can't write to the external SD with the Tab connected to my computer. With a small file, the progress bar immediately jumps to 100% but then freezes and after a long time the copy times out with the message, "The device has either stopped responding or has been disconnected". With a large file the progress bar plods along, first at a normal speed but gradually getting slower and slower, until at some point it stops moving and the copy times out.
Please, I beg of you, help me exorcise my demon Tab!
SOLUTION: Before actually posting this plea for help, I re-formatted my SD card (in the Tab) and all functionality is restored. I post this at risk of making myself look like an idiot, in hopes that it might save someone else's hair.
Good on you for posting the problem and the solution. I doubt you'll be the only person to experience this.
Sent telepathically to my Galaxy S4
droidmark said:
... I post this at risk of making myself look like an idiot, in hopes that it might save someone else's hair....
Click to expand...
Click to collapse
From that comment it seems we need more bald users as no risk testers.
Sent from my Nexus 10 using XDA Premium HD app
droidmark said:
When I tried to write a file to my Galaxy Tab Pro 8.4's external SD card with Astro and it wouldn't work I was flustered. A little research turned up the crippled SD support in KitKat and how to fix things with the simple platform.xml hack. I did that, and all was right with the world again.
Then I got another 8.4, and actually cloned the first one to the second one with a nandroid backup. I also moved my SD card from the first to the second. Eventually I sold the first one and am just left with the second one. But somewhere along the way I lost the ability to write to the SD card, and I can't get it back!
The hacked platform.xml file was of course cloned along with everything else, but it just doesn't work. What's just as bad, or worse, is that apps which should write to external SD even without the hack (and which did, prior to this issue developing), such as Samsung's My Files, and Root Explorer, also are no longer able to!!!!
So to try and fix things, I flashed this ROM to my Tab: http://forum.xda-developers.com/showthread.php?t=2698460 But I still can't write to external SD, even with My Files!
Here's another problem, which may or may not be related: I also can't write to the external SD with the Tab connected to my computer. With a small file, the progress bar immediately jumps to 100% but then freezes and after a long time the copy times out with the message, "The device has either stopped responding or has been disconnected". With a large file the progress bar plods along, first at a normal speed but gradually getting slower and slower, until at some point it stops moving and the copy times out.
Please, I beg of you, help me exorcise my demon Tab!
SOLUTION: Before actually posting this plea for help, I re-formatted my SD card (in the Tab) and all functionality is restored. I post this at risk of making myself look like an idiot, in hopes that it might save someone else's hair.
Click to expand...
Click to collapse
Just wanted to add a postscript for anyone who might have a similar issue. I thought this problem was solved, as described above. Then a few days later when I booted up my tab, the SD card was shown as blank/unformatted. At that point I did some more digging and determined that it was actually a counterfeit 32GB card, based on an 8GB card. Got a refund, threw it in the trash and ordered a new 64GB card. Caveat emptor!
Hello. I have a Galaxy S3 (SGH-I747 on Rogers Canada) with android 4.4 - stock/not rooted. The other day I hooked up my S3 to my laptop using a USB cable. My laptop is running Win XP SP3. I COPIED ALL the pictures from the phone to the Laptop. The pics were visible on BOTH my phone and my laptop when I finished the transfer. I am guessing it used Windows Media as the transfer medium as Kies was not running. While the phone was still linked to the Laptop I thought I would just delete the ones off the phone that I didn't want. I did so. I then unhooked the phone from the laptop. Ouch!!! The pictures I had deleted from the phone were missing from BOTH the phone and the laptop. First I checked the laptop trash bin. Nothing there. I then tried using the Recuva undelete software on my laptop disk as I thought there should be a deleted copy on the disk as they were visible on screen before I unplugged my phone. It recovered some 94k plus jpg's and I spent more than a day scanning them for the ones I needed. Nothing there. So I thought I needed to run an undelete on the phone. HA HA to that!!! It seems that in the android developers great wisdom the phone is no longer considered a mass storage device when hooked to a computer but is a media device. MY interpretation but something like that. Next I did a BUNCH of reading and made a bunch of phone calls for advice. I tried all kinds of tricks. I tried a number of android undelete programs. I had the USB debugging enabled but all the programs I tried didn't recover any deleted jpg's. Even the programs that said they could. It turns out that the phone HAS to be linked as a mass storage device with a drive letter for the android recovery software to work to recover jpg's. It seems to be able to find other file types but not jpg's.
Now here is the interesting part. I tried linking the phone to my desktop (XP SP3 also) and my laptop dozens of times hoping something would change. I believe that once on my desktop and once on my laptop it showed up as a mass storage device. I say "I believe" because I was so conditioned to it NOT showing as a mass storage device that both times I had already clicked on the icon that releases the phone from the computer before I realized there was a drive letter there. Anyway, the time on my laptop that it happened was around the time I had run one of the android file recovery programs. The program had not found any jpg files but when it finished my phone had a message something like "SE has been disabled". blah blah blah. I did a BUNCH more reading and researching about SE on my phone. The best I can figure is that it is a security enhancement designed to stop programs getting at, or changing things in, other programs on the phone and is set somewhere in the policies file - where ever that is.
My question is - Is it possible to temporarily disable SE so I can try and get my pictures back? Thank you, Derek-j
derek-j said:
Hello. I have a Galaxy S3 (SGH-I747 on Rogers Canada) with android 4.4 - stock/not rooted. The other day I hooked up my S3 to my laptop using a USB cable. My laptop is running Win XP SP3. I COPIED ALL the pictures from the phone to the Laptop. The pics were visible on BOTH my phone and my laptop when I finished the transfer. I am guessing it used Windows Media as the transfer medium as Kies was not running. While the phone was still linked to the Laptop I thought I would just delete the ones off the phone that I didn't want. I did so. I then unhooked the phone from the laptop. Ouch!!! The pictures I had deleted from the phone were missing from BOTH the phone and the laptop. First I checked the laptop trash bin. Nothing there. I then tried using the Recuva undelete software on my laptop disk as I thought there should be a deleted copy on the disk as they were visible on screen before I unplugged my phone. It recovered some 94k plus jpg's and I spent more than a day scanning them for the ones I needed. Nothing there. So I thought I needed to run an undelete on the phone. HA HA to that!!! It seems that in the android developers great wisdom the phone is no longer considered a mass storage device when hooked to a computer but is a media device. MY interpretation but something like that. Next I did a BUNCH of reading and made a bunch of phone calls for advice. I tried all kinds of tricks. I tried a number of android undelete programs. I had the USB debugging enabled but all the programs I tried didn't recover any deleted jpg's. Even the programs that said they could. It turns out that the phone HAS to be linked as a mass storage device with a drive letter for the android recovery software to work to recover jpg's. It seems to be able to find other file types but not jpg's.
Now here is the interesting part. I tried linking the phone to my desktop (XP SP3 also) and my laptop dozens of times hoping something would change. I believe that once on my desktop and once on my laptop it showed up as a mass storage device. I say "I believe" because I was so conditioned to it NOT showing as a mass storage device that both times I had already clicked on the icon that releases the phone from the computer before I realized there was a drive letter there. Anyway, the time on my laptop that it happened was around the time I had run one of the android file recovery programs. The program had not found any jpg files but when it finished my phone had a message something like "SE has been disabled". blah blah blah. I did a BUNCH more reading and researching about SE on my phone. The best I can figure is that it is a security enhancement designed to stop programs getting at, or changing things in, other programs on the phone and is set somewhere in the policies file - where ever that is.
My question is - Is it possible to temporarily disable SE so I can try and get my pictures back? Thank you, Derek-j
Click to expand...
Click to collapse
This is the international i9300 area, to save you posting this long message again I will get a Mod to move it for you to the i747 area but I wish you the best of luck.
SElinux stands for "security enhanced Linux" and turning it to permissive will not do a lot I believe. However this app can enable UMS on your phone again. Here is the link https://play.google.com/store/apps/details?id=com.mohammadag.samsungusbmassstorageenabler
Thank you...
crazymonkey05 said:
SElinux stands for "security enhanced Linux" and turning it to permissive will not do a lot I believe. However this app can enable UMS on your phone again. Here is the link - deleted...from response
Click to expand...
Click to collapse
Alright...thank you crazymonkey!!! Will give it a shot and report back with results.
Derek-j
Back to square one!
crazymonkey05 said:
SElinux stands for "security enhanced Linux" and turning it to permissive will not do a lot I believe. However this app can enable UMS on your phone again. Here is the link deleted to respond.
Click to expand...
Click to collapse
Oooppss...not going to work. First off...my phone is stock and this requires rooting. I don't know much about rooting and don't have a problem trying it but I suspect that would likely over-write some or all of the deleted jpg's I want to recover thus defeating the purpose. The other and absolutely CRITICAL thing is that it does NOT enable USB for internal memory. You'd think that the GOOGLE developers would know better than to remove that important feature, especially in an (upgrade???). I had even thought of going back to one of the older versions but again I think that would destroy some of the file entries and delete the very pics I am trying to get back....
I REALLY DO APPRECIATE your trying to help though.
Have a FANTASTIC week. Derek-J.
So BACK TO SQUARE ONE...Anyone know how to temporarily disable the SE feature?
derek-j said:
Oooppss...not going to work. First off...my phone is stock and this requires rooting. I don't know much about rooting and don't have a problem trying it but I suspect that would likely over-write some or all of the deleted jpg's I want to recover thus defeating the purpose. The other and absolutely CRITICAL thing is that it does NOT enable USB for internal memory. You'd think that the GOOGLE developers would know better than to remove that important feature, especially in an (upgrade???). I had even thought of going back to one of the older versions but again I think that would destroy some of the file entries and delete the very pics I am trying to get back....
I REALLY DO APPRECIATE your trying to help though.
Have a FANTASTIC week. Derek-J.
So BACK TO SQUARE ONE...Anyone know how to temporarily disable the SE feature?
Click to expand...
Click to collapse
I don't think you can on Android 4.4 without root. Why not just go towel root your S3?
Yea there is not much you can do without root, sorry for your troubles
Hello,
today, when trying to update my apps, I was told by Google Play that my phone's internal storage was completely full and it was thus impossible to install any updates.
Seeing as everything had worked perfectly fine a few days prior and I hadn't done anything exceptional that would merit multiple gigabytes of storage space to be used, I was completely baffled by this.
I opened ES Explorer and made it analyse my internal SD card, and it came up with two huge thumbnail files in my "Pictures" folder, each being around 2GB in size. I deleted them and thought my problem to be fixed. Nope. Still the exact same error message, even after rebooting. Another analysis of my storage came up with (and I'm sorry for not posting a picture, but it wouldn't let me due to spam-prevention measures) the following:
Near the bottom of the screen, it says in red "Used/Occupied: 10,18 GB", but the top-most window, listing all folders, shows that ES was only able to come up with around 6.3GB of data. Somehow, there are almost 4GB missing!
I wasn't sure if hidden files were being taken into consideration as well, so I skimmed through most hidden folders myself, trying to come across something, but according to my findings, everything should be working perfectly fine.
Has anybody had this problem before, and if so, how did you fix it?
Thanks in advance!
haiyyu said:
Hello,
today, when trying to update my apps, I was told by Google Play that my phone's internal storage was completely full and it was thus impossible to install any updates.
Seeing as everything had worked perfectly fine a few days prior and I hadn't done anything exceptional that would merit multiple gigabytes of storage space to be used, I was completely baffled by this.
I opened ES Explorer and made it analyse my internal SD card, and it came up with two huge thumbnail files in my "Pictures" folder, each being around 2GB in size. I deleted them and thought my problem to be fixed. Nope. Still the exact same error message, even after rebooting. Another analysis of my storage came up with (and I'm sorry for not posting a picture, but it wouldn't let me due to spam-prevention measures) the following:
Near the bottom of the screen, it says in red "Used/Occupied: 10,18 GB", but the top-most window, listing all folders, shows that ES was only able to come up with around 6.3GB of data. Somehow, there are almost 4GB missing!
I wasn't sure if hidden files were being taken into consideration as well, so I skimmed through most hidden folders myself, trying to come across something, but according to my findings, everything should be working perfectly fine.
Has anybody had this problem before, and if so, how did you fix it?
Thanks in advance!
Click to expand...
Click to collapse
I've had this problem happen to me once on a previous Android phone. I ended up performing a factory reset and it worked fine after that.
Our family took the technically free at&t deal to switch to the galaxy s22 phone (256 GB model) by trading in our galaxy s7 phones, and I've been tinkering with the settings, turning a whole host of stuff off because forget auto-installing apps and whatnot, but when I was copying my old phone's pictures over manually (forgot about smart switch, sue me [but don't pls]), the process slowed down very much. Every 15 seconds or so, my windows would give the Asterisk sound, but the green progress bar wouldn't make it past the 1% mark, and when trying to close the file window on my desktop, it'd take the same 15 seconds time to do so, and to stop this I had to unplug the phone from my desktop. Then I had to upload everything to dropbox and download it through the app onto my phone just to export it that way.
Since im still making sense of the phone, is there a concrete reason behind this slowdown, some phone setting or whatnot, because i uninstalled/reinstalled the Samsung USB Phone/Device Drivers from the software downloads portion of samsung, and there's no speed increase. My galaxy s7 was faster, so unless this is a quirk of the firmware itself or something else....idk, help pls?
One or more of the files may be corrupted.
I ran into this the other day on my N10+ going from SD card to a OTG flashstick with a 50gb folder with more than a dozen subfolders and 20 loose media files. It kept crashing on the last 2 or 3gb. I tried copying a couple different ways, nothing worked until I discovered a corrupted avi file and deleted it.
Copied it straight up.
Find the root cause, it could be malware that inadvertently got downloaded. This includes jpegs.
I doubt its malware, all the pictures I did were from the default camera app on my old phone, and I figure if I did it through smart switch it wouldn't have any problems, but ill look through my pictures, delete some, maybe put mcafee livesafe on there and run a few scans to see if it picks up anything before I uninstall it (seriously, the app is a resource hog no matter what hardware its on, mobile or not). ill make another reply if I find some kind of resolutiuon and result(s)
LodeUnknown said:
I doubt its malware, all the pictures I did were from the default camera app on my old phone, and I figure if I did it through smart switch it wouldn't have any problems, but ill look through my pictures, delete some, maybe put mcafee livesafe on there and run a few scans to see if it picks up anything before I uninstall it (seriously, the app is a resource hog no matter what hardware its on, mobile or not). ill make another reply if I find some kind of resolutiuon and result(s)
Click to expand...
Click to collapse
Never use SmartSwitch to backup critical data especially media. Never clone media files ie music databases. Never password protect backups. Keep it rock stupid simple.
Copy/paste then compare size, and folder/file count. Inspect at least some of the data for readability.
Malware is always possible. The scripted jpegs on Android tend to only effect the folder they're in. Was that avi file I found malware? Who knows? I don't care as I just delete it and move on unless it raises its ugly head again. The point is I found the cause and removed it.
The scripted Android jpeg I encountered did it's thing when opened. It damaged many loose files but no files that where in folders. Some files I repaired, the rest I deleted. The malware jpeg I deleted first though and it was only by cause and effect that I found it. Fortunately it was the download folder so it's reign of terror was brief; had that been a large database it could turn into a digital blood bath.
All downloads go to the download folder and stay there until vetted. Check all files by opening them there before moving them elsewhere. Delete any unknown ones without opening. Any file that is in doubt especially apks, executables scan with online Virustotal.
Keep email in the cloud ie Gmail.
I'm running on Pie but haven't had any malware damage in over 2 years and it's in part because of how I handle all downloads... carefully.
I did mine manually, I never touched smart switch for my phone, but I did a scan with the mcafee security app on my phone, and it didnt find anything sketchy on there, used the at&t mobile security app that was on there before I uninstalled it (adb is da best :3 ) and it didnt find anything hinky. I scanned the manual backups of my pictures on my desktop with mcafee livesafe and superantispyware and neither of them found anything bad, unless i should use more scan programs, but whether its on my phone or desktop, I think I got enough, anymore and im just hoarding antivirus programs, and I don't wanna do that
LodeUnknown said:
I did mine manually, I never touched smart switch for my phone, but I did a scan with the mcafee security app on my phone, and it didnt find anything sketchy on there, used the at&t mobile security app that was on there before I uninstalled it (adb is da best :3 ) and it didnt find anything hinky. I scanned the manual backups of my pictures on my desktop with mcafee livesafe and superantispyware and neither of them found anything bad, unless i should use more scan programs, but whether its on my phone or desktop, I think I got enough, anymore and im just hoarding antivirus programs, and I don't wanna do that
Click to expand...
Click to collapse
Over the years I found 2 scripted jpegs that were found by observing what happened when they were opened. There's no guarantee malware will be detected.
I ran a Malwarebytes scan occasionally. It found a trojan preloader I missed in the download folder, which I police daily now. This one downloaded itself, it slipped through the Samsung browser in spite of settings.
On Android antivirus is a waste of resources. Most victims install or download the malware themselves.
However anytime Android behaves strangely malware should be considered a possibility.
No idea how that file that screwed up my transfer got corrupted or if it was malware.
It acted like malware, regardless, deleting it fixed the issue. It took some time to track it down. Point being when you see odd behavior you don't ignore it, you find the root cause.
I think I fixed it somehow? I searched for reset in the settings and found reset network settings, reset accessibility settings, and reset all settings, so I chose reset all settings after backing up my current settings. After my phone restarted, I plugged in my phone and tried copying a 500MB sized file to my internal storage, and despite it taking a full minute, it actually finished without the problems I had before. Granted, now it seems only for the one file I just did, because after I tried one file and tried to do another, it stopped about halfway into copying a 400MB range file and gave me the same problems again. ffs fml
hopefully this is my last post (I swear if it isnt im tearing up the cable I got), because after trying multiple cables we got and different usb ports, I think I identified the culprit(s): my USB-C cable (the one I use to charge it) and my desktop's front-facing USB ports.
My desktop is an XPS 8700, and its taken on some age and some injuries due to power surges and what not, most of all the front-facing USB ports are wiggly as all hell, and occasionally choose which cables to like and which to not like. So I took the cable I usually use to charge it with and plugged it into a different usb port and tried copying over a set of files totaling 1GB+change to the internal storage, lo and behold, it copied over and no stopping halfway and cancelling the transfer because of it. Then I tried another USB-C cable we got (from a different piece of hardware) and used it on my front-usb ports, did the same thing again, 100% completion like the others did
The end result is my desktop being an ornery POS as usual and choosing which USB port likes which USB cable no matter how good I take care of both pieces of hardware. In the end, ill probably be getting a few more cables for our three phones and keep the cable I usually use with it for a different piece of hardware. This was one rabbit hole of a goose chase