Galaxy Device Encryption application.
I downloaded yesterday and encryted the galaxy s2. I really admired the encryption process.
The problem is that, when I decrypted it, the phone rebooted and all my applications are gone. It was as if the phone has been hard reset. I still see that my system storage still has the applications as the size has not changed. However I cannot install any new application and I really need your help. I have done all that I know as a computer engineer.
I need your help and I know you can help me. Thank you for your antiscipated favour.
Personally don't know. Have you checked with the application developer?
Should done a full backup before such a risky maneuver.
This is a problem with most of the new ICS roms out now
Both my AT&T S2 and my Kindle Fire are both hanging on the encryption provision (needed for Outlook). We think it may be due to all the apps being downloaded first before we config the phone/tablet. In some cases, there isn't much room left. So I am trying that now..
Any help here would be great.. I get just the Droid, no output of progress.
fromnana said:
Galaxy Device Encryption application.
I downloaded yesterday and encryted the galaxy s2. I really admired the encryption process.
The problem is that, when I decrypted it, the phone rebooted and all my applications are gone. It was as if the phone has been hard reset. I still see that my system storage still has the applications as the size has not changed. However I cannot install any new application and I really need your help. I have done all that I know as a computer engineer.
I need your help and I know you can help me. Thank you for your antiscipated favour.
Click to expand...
Click to collapse
There are two things that you can try, if not tried yet...
I'm not sure this would work or not but it's worth a shot.
one is that you can use a root file browser ( like Root Explorer or anything ), browse the data partition and if you find applications in the app directory copy it (if not all then at least data/app and data/data directories) to some external card then do a data wipe and copy these back...
another way could be that you try out the Titanium backup app and see if it is able to list out your apps...if it does then back them up and do a data wipe and restore that backup.
And you might also consider using some third party launcher......it might also list out all your apps and if it does .....then just clear the data/cache for TWlauncher and then you might see your apps again...
Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.
Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.
I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.
4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium
No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.
Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?
I fixed this deleting the "pictures" folder with RootExplorer.
jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .
My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!
Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.
Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0
/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk
Hey everyone!
I have a AT&T Samsung Galaxy Note II SGH-i317 build UCAMC3 rooted supersu running stock 4.1.2 and stock recovery. Basically all I've done is root it (using odin and an autoroot .zip from a guide I found) and everything works fine and no problems and imei is there and modems all working etc.
I've been trying to back up my efs file before flashing CWM and XenonHD11.1. I've tried TONS of methods and I haven't been able to get any of them to work. Methods include efs pro v1.9 and v2.0, using terminal emulator, and two or three different tool kits. Oh and I think one used odin if I remember right (maybe not, not important I guess). I've also looked for an app but haven't found one that supports my model. Anyone have a solution or suggestion?
More info:
I'm also having other issues that could very well be effecting my being able to use efs pro and tool kits to backup efs:: My Windows XP SP3 won't install drivers for my phone: Drivers downloads> drivers installs> phone connects (tried usb debug mode and normal)> driver install error "The required section was not found in INF". So EFS Pro (both versions) don't detect phone at all. Odin does detect it fine (weird). Toolkits don't detect phone at all.
Terminal Emulator doesn't find any files or directories that any guide that I've found says to use (weird?).
If rooted...
Use a root capable file explorer application. ..(root explorer app works great)...
Once inside the application. ..grant it root access. ..
Then enable R/W Access in the application setting at the top of the screen. ..
Then navigate to your EFS folder. ..
Long press the folder. ..and select "copy" from the drop down menu...
Then navigate to your SD card...
Hit the menu selection button at the top of the screen. ...and select "paste"...
Allow the file to copy. .then verify you have created a successful copy by backing out of the application and opening it again. ...and navigating to the SD card...
You should see the copy. ..
Warning. ..
Root access applications can be dangerous if you are unfamiliar with the layout or the ramifications of playing inside of protected system files. ..
Practice on a non critical file like a picture or music file first...before moving or copying anything critical. ..
Enjoy. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Thank you! And thank you for the warning advice too! Great idea to practice! I haven't tried it yet but I'm going to soon when I get a chance. I ended up reading and finding out that doing a nandroid backup also backs up efs along with everything else and that cwm and twrp's backup makes a nandroid backup. So I chanced it and flashed cwm via Odin and everything was fine and I did a couple backups of stock rom and build and kernel and all and then flashed XenonHD with halo and I LOVE it! Thank you again!
Sent from my SAMSUNG-SGH-I317 running XenonHD 11.1 with Halo using xda app-developers app
sgh-i317 EFS seems like its gone
would it be posible to get a copy of the efs files.
out of nowhere it seems like the efs file just went missing. ive finally got to were i can look thru system files but its no wear to be found,
there not much i can do at this point that i know of, it seems like the efs files that are missing are keeping it from booting up. right now the only thing it will do is hang at the att logo, im on the mk6 with the knox counter. .but i cant figure out what els to do...
any advice would gratefully be appreciated and would be my hero.
Just looking for a definative answer. One I didn't know about the HTC one m8. I'm in the process of rooting the phone be doing it later when I get home. But I downloaded viper Rom anyway to have it on the Phone to save flashing time. It downloaded onto internal memory as normal. But I cannot move it to my external ad card. Using es file explorer. After a little searching from what I can grasp is I have to do it through pc. Is it true
I also found out that I can easily do it after rooting. But if I root I loose the file. Yes I know I can save it to pc and transfer later but I find it strange I cannot moves files like normal on any other phone and this is me coming from the galaxy s4
snwman said:
Just looking for a definative answer. One I didn't know about the HTC one m8. I'm in the process of rooting the phone be doing it later when I get home. But I downloaded viper Rom anyway to have it on the Phone to save flashing time. It downloaded onto internal memory as normal. But I cannot move it to my external ad card. Using es file explorer. After a little searching from what I can grasp is I have to do it through pc. Is it true
I also found out that I can easily do it after rooting. But if I root I loose the file. Yes I know I can save it to pc and transfer later but I find it strange I cannot moves files like normal on any other phone and this is me coming from the galaxy s4
Click to expand...
Click to collapse
Why do you lose the file after rooting? All files stay intact after rooting on my device. It's unlocking the bootloader that wipes everything.
ashyx said:
Why do you lose the file after rooting? All files stay intact after rooting on my device. It's unlocking the bootloader that wipes everything.
Click to expand...
Click to collapse
Well I still have to unlock bootlader yet forgot to mention that
Newbie question, forgive me if it's dumb. I have a Galaxy Tab T310 that I just rooted because I wanted to be able to get around the SD card write issue. BUT, the real problem I have is that I want to simply copy movies from my desktop to the Tab via a USB cable but the Tab keeps erasing the files. It doesn't erase the directories I create on the SD, it just erases the files IN the directories and often the subdirectories. Sometimes it erases them as soon as I copy new files to the SD, sometimes when I reboot the phone. But it always erases them.
I'm assuming this is related to the Android security effort to "protect me," but I don't know how to keep it from happening. Will one of the root apps like SDFix keep this from happening? Again, I'm not talking about apps being able to write files to the SD, I'm just talking about me being able to write files to the SD using a cable and then KEEPING the files from being erased by the Tab. Thanks for the help!
Auto-delete files
Can anyone point me toward another forum where I might find an answer to this question? I thought this would be the best place but apparently I am the only person who has ever seen this problem. This makes me wonder whether there is another problem with the tablet....
k9bm said:
Newbie question, forgive me if it's dumb. I have a Galaxy Tab T310 that I just rooted because I wanted to be able to get around the SD card write issue. BUT, the real problem I have is that I want to simply copy movies from my desktop to the Tab via a USB cable but the Tab keeps erasing the files. It doesn't erase the directories I create on the SD, it just erases the files IN the directories and often the subdirectories. Sometimes it erases them as soon as I copy new files to the SD, sometimes when I reboot the phone. But it always erases them.
I'm assuming this is related to the Android security effort to "protect me," but I don't know how to keep it from happening. Will one of the root apps like SDFix keep this from happening? Again, I'm not talking about apps being able to write files to the SD, I'm just talking about me being able to write files to the SD using a cable and then KEEPING the files from being erased by the Tab. Thanks for the help!
Click to expand...
Click to collapse
k9bm said:
Can anyone point me toward another forum where I might find an answer to this question? I thought this would be the best place but apparently I am the only person who has ever seen this problem. This makes me wonder whether there is another problem with the tablet....
Click to expand...
Click to collapse
You might try downloading an SD Card Fix app from the Play store. There are several of them. KK messed up the ability to copy to the Ext SD card.
If you're rooted, then download ES File explorer app. Run it and hit your menu button. Scroll down the menu and make sure Root Explorer is checked.
That's all I can think of that might help