One of the first things I did on buying my new Galaxy Tab 2 7" (GT-P3100, Wi-Fi and 3G; Spanish market "PHE" identifier, came with ICS 4.0.3, no updates available either through Kies nor OTA) was to encrypt the Device. It worked.
Then I rooted the device with CF-Auto-Root, which had the side effect of performing a factory reset, and as I understand it from a brief conversation with the author of (the excellent!) CF-Auto-Root this was an expected side-effect of the device having been encrypted at the time of applying CF-Auto-Root.
So, the Tab 2 is back to un-encrypted.
Here are the details:
Android 4.0.3
Baseband version 3.0.8-CL448962-user [email protected] #1
Build number IML74K.P3100XWALD2
But now I'm trying to encrypt again (either/both the SD Card and the Device itself) and I'm having no success at all.
On trying to encrypt the SD card, each time it always returns "SD Card Encryption Error" within a few seconds. (And indeed thereafter I always get a Notification about "SD card encryption error" any time the SD card is mounted by the device). If I go back to Settings -> Security -> Encrypt SD card and select to decrypt the card (even though it's not really encrypted), then I can access the SD Card again - no damage was done (and no encryption either).
If I try to encrypt the Device, I get the black background with the large green outline android, and ... nothing. The green android on the black background just stays there. After the normal screen timeout, the screen goes completely blank; I tap the power button, get the usual unlock screen, unlock it, see the green android again ... and, nothing. If I rotate the tablet, the android rotates. If I tap the power switch, I get the silent/ flightmode/ reboot/ turnoff menu. But nothing will get me back to the normal user interface, and it never finishes encrypting (I really think it never starts).
Eventually (after more than a couple of hours) I give up, tap the power switch and select to reboot, and it comes back up fine, but not encrypted.
One of my main reasons for getting the newer device was to have encryption :-/
Is Encryption (Device, and SD Card) supported/ functional when CF-Auto-Root is in use on a Samsung Galaxy Tab 2 (Android 4.0.3)?
How do I get encryption to work, for both the Device and the SD Card?
Is there a way to get more detailed logging (the Tab is rooted, and I have command line access) and/or to command the encryption from the command line, to see what's really happening?
Thanks!
Hm, I tried encrypting only NEW files on the SD Card now, and that seems to work.
I stored a new file on the SD Card, unmounted the card from the Tab, put the card in a card reader on a desktop computer, and indeed the contents of that file are just "data", not readable. Back in the Tab, the contents are the picture which I'd saved to the card.
But still attempting to encrypt the existing files on the SD Card fails. And still attempting to encrypt the device does nothing (green android appears, but no % complete ever displays, etc, just as I posted before).
One step further with the external SD Card; I copied off all of the data, formatted the card, and then was able to fully encrypt it (and copy back my data).
But the Device itself, I still can't encrypt at all - just the same as before.
No ideas? None? Nobody? Please....?
Thanks,
-Jay
Bump?
sigh
Try the same thing with the device itself.
Do a factory reset.
Not once,twice.
I know u lose all data.
But try it.
And do this without android to start.
Keep press power+vol up.
Get into menu and do factory reset,wipe dalwik...all.
Hope this help.
libove said:
If I try to encrypt the Device, I get the black background with the large green outline android, and ... nothing. The green android on the black background just stays there. After the normal screen timeout, the screen goes completely blank; I tap the power button, get the usual unlock screen, unlock it, see the green android again ... and, nothing. If I rotate the tablet, the android rotates. If I tap the power switch, I get the silent/ flightmode/ reboot/ turnoff menu. But nothing will get me back to the normal user interface, and it never finishes encrypting (I really think it never starts).
Eventually (after more than a couple of hours) I give up, tap the power switch and select to reboot, and it comes back up fine, but not encrypted.
Thanks!
Click to expand...
Click to collapse
Did u solve the problem?
i have the same problem
MasterBrush said:
Did u solve the problem?
i have the same problem
Click to expand...
Click to collapse
This was over a year ago, and I don't even use the device anymore. Sorry, can't help.
I've since then tried a ZTE "Skate Pro" (the Movistar Spain branding of the "Blade III"). Piece of Sh*t phone. Support encryption natively under Android 4.0.4, but if you do encrypt the phone, the performance of the touch screen becomes unreliable, frequently so bad that swiping (including Swyping) actions don't work right, and you end up less moving things on the screen and more, effectively, tapping things you absolutely did not intended to tap. I discarded the ZTE Skate Pro/ Blade III.
Then I tried a Haier W708, dirt cheap; not a powerhouse, but satisfatory.
And a Nexus 5 which kicks *ss all over the place.
I can't help any more with this thread, and any results in this thread would not longer help me, so I'm dropping off the thread now.
Best of luck to all.
Related
I was installing my invisibleSHIELD last night with my phone turned off, and apparently managed to do something while trying to fiddle it on as the screen turned on with some small amount of data, and it was colored like some color test screen, red blue green and white horizontal areas(or something like that).
So what did I manage to do? Was it dangerous in anyway for the phone? Probably not, but I'd like to know how I did it and what's its purpose =)
This is called the bootloader screen (popularly known as the Tri-colour screen), you got to this screen by starting up the phone with the Volume Down button held.
Not dangerous at all, unless you had a RAPHIMG.nbh file on the root directory of your fat32 formatted storage card
[along with a wrapper] (Having that file in the root and starting up to the bootloader would allow one to initiated a flash)
This mode is used to flash a new rom, radio or spl to the device, either run to it automatically by a Wrapper from your computer or forced by the user. From this screen one can even flash any of those items from a storage card instead of from the computer. (I do this from time to time when I dont have access to a computer with active sync and wish to flash a rom.
Of course, one needs hard spl to flash anything custom.
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
jallweiss said:
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
Click to expand...
Click to collapse
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
buhohitr said:
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
Click to expand...
Click to collapse
Thanks buho,
Full power drain and repower didnt seem to fix it.
I gave it a shot with the update and I still got the message saying that the signature matched and then freezing at the bootloader trying to use the update. As I edited in my post I found that the bootloader commands had been swapped, so I can get to the other options to work. However all of them freeze the bootloader, I cant get any kind of USB recognition at all.
Unfortunately things may have gotten even worse...
I figured since I just need the device to work I would do a full wipe, I started the data wipe, got the freeze after a bit of text. I left the device for about 20 minutes hoping it would go through with the wipe. It was still frozen on the bootloader so I reset the device again... After resetting I cant even get into the bootloader anymore, power button + volume down does nothing.
So currently Im stuck on the first splash screen, unable to access the bootloader. I would appreciate any help at all.
Just to update, I can get APX mode to function right now, but I am not really sure where I can go from there...
Hi Everyone! This is my first forum post anywhere (I'm used to looking at these forums, but not asking questions), as this issue has me completely stumped.
The issue is that every time the Nexus 5 (32 GB - White) is started, no matter what ROM I use, the first screen always works just fine. However, if I were to hit the power button to lock the device, it doesn't unlock. If I hit the bottom arrow, it will immediately lock the screen; when it gets to the "Select Wifi Network" screen, the screen unlocks. At that point, hitting the power button will show a glimpse of the screen, then immediately lock.
If I am in either Clockwork Recovery, or TWRP recovery, there are no issues at all. The issue is only present whenever I am actively in an operating system.
Things I have tried so far: using fastboot to copy over Google's stock images back. They all replicate the issue as well... I was on Android L Preview, and started noticing the issue. First thing I did was try to fastboot the image of the 2nd to latest image (the latest one had knocked out the front facing camera for some reason... lol). I have tried both Clockwork Recovery and TWRP as alternate recovery options and tried to sideload CM 11, and that didn't do anything. I have tried clearing any partition to clear it.
Well, after all of this, I called Google, and they told me I had voided my warranty, so I decided to go ahead and open up my phone to check for any damages, and the water indicator on the inside of the phone was set off (pink). However, there wasn't any damage except for some corrosion (sweat, I am pretty sure), but that which could be found was removed.
I'm at a complete loss. Is there a reason the recoveries would work flawlessly, but the OS fails when you try to use it? Is there a way to truly nuke the entire storage device on the inside, recreate the partitions, reinstall recovery, and maybe have a completely wiping any trace of the OS? It feels like something might be staying in all the erases I have done.
Thanks much for the help in advance!!!
Strange issue with my phone. Got off the plane in KC, turned it on, then walked into the terminal. Was using work email and hit the home button to get back to the home screen. Nothing. Recents button doesn't work either.
Rebooted the phone and everything works. 10 minutes later, home button and recents (left soft key) stop working. Another reboot, good for 10 minutes, same problem.
I want to do a factory reset, but work forces me to encrypt my SD card. I uninstalled AirWatch, go to Decrypt SD card in security settings. Get to the page to execute the decryption and push "Decrypt SD card". Nothing happens. Thinking it might be a dead zone at the bottom of the screen because the button was right above the home button, I flip the phone 90 degrees. Press "Decrypt SD Card", nothing.
Now I can't factory reset or I can't access my SD card.
Thoughts?
cjranucci said:
Strange issue with my phone. Got off the plane in KC, turned it on, then walked into the terminal. Was using work email and hit the home button to get back to the home screen. Nothing. Recents button doesn't work either.
Rebooted the phone and everything works. 10 minutes later, home button and recents (left soft key) stop working. Another reboot, good for 10 minutes, same problem.
I want to do a factory reset, but work forces me to encrypt my SD card. I uninstalled AirWatch, go to Decrypt SD card in security settings. Get to the page to execute the decryption and push "Decrypt SD card". Nothing happens. Thinking it might be a dead zone at the bottom of the screen because the button was right above the home button, I flip the phone 90 degrees. Press "Decrypt SD Card", nothing.
Now I can't factory reset or I can't access my SD card.
Thoughts?
Click to expand...
Click to collapse
Will it let you copy SD contents to a PC?
Then you could just wipe and copy back / encrypt again
*Detection* said:
Will it let you copy SD contents to a PC?
Then you could just wipe and copy back / encrypt again
Click to expand...
Click to collapse
Hmmm, so it would decrypt to copy? Are you sure I wouldn't get an encrypted copy on my PC, then wipe the phone and be unable to decrypt? I guess if I can see the files on my PC, then they have to be decrypted....
cjranucci said:
Hmmm, so it would decrypt to copy? Are you sure I wouldn't get an encrypted copy on my PC, then wipe the phone and be unable to decrypt? I guess if I can see the files on my PC, then they have to be decrypted....
Click to expand...
Click to collapse
That's what I'm saying, find a way to copy them obviously decrypted, to the PC, then you can wipe and sort everything out
Afaik the main storage on the S7 is encrypted by default, and it has no problems copying things from there to PC decrypted
Can't speak for SD Card, not tried
*Detection* said:
That's what I'm saying, find a way to copy them obviously decrypted, to the PC, then you can wipe and sort everything out
Afaik the main storage on the S7 is encrypted by default, and it has no problems copying things from there to PC decrypted
Can't speak for SD Card, not tried
Click to expand...
Click to collapse
So that worked. Data is over on my PC and I can read it, so it is not encrypted. Perfect, right?
Time to factory reset. Go into settings and click the box to format the SD card as well and hit factory reset. Nothing. Nothing happens. What the hell is going on here? Can't use Home or Recents button, can't decrypt SD card, can't perform a factory reset. Malware?
Just going to reset it from the recovery menu I guess.
cjranucci said:
Just going to reset it from the recovery menu I guess.
Click to expand...
Click to collapse
No idea what's wrong, possibly just something has corrupted, strange one, have you got any screen overlay apps installed like blue light filters? They can do that
If you can view, open, read the files on the PC they're no longer encrypted
I noticed yesterday that indeed the home button and menu/recent buttons were working strangely
- HOME opened the google now, even though Apex is the default home app
- Menu opened recent, both with long and short click
After a reboot this seems to be corrected, but I still find it strange. Not rooted that device either.
Late response but my s6 and s7 have had this happen with airwatch. Something glitches when time to change my pin.
The phone will just turn off, screen only. Turn it on, log in and home and recent buttons don't work. Trying to manually change the pin will make the soft keyboard not come up so you cant change pin/pass, but clipboard works if you happen to have something useable in there.
Best option, although I am one of the admins, is launch chrome, request desktop, go to our airwatch portal and clear/force a pin change. Phone flickers and home/recent works again. I have to do this every 60 days or so. It's happened 4 times now.
Maybe there's a UFO near you.
Joking aside, do you have Direct access turned on and set up, under Settings - Accessibility?
Hello everyone!
Yesterday I powered off my Moto G3 and plugged it in to charge. After a few minutes I heard a short vibration, which normally means that the phone powered on by itself and is booting. I then checked the screen; I had to put in the PIN for my SIM card, but afterwards there was no pattern I had to draw in order to unlock the phone (I had one set up before!). After unlocking the screen I can see a blue screen with "Welcome" at the top, a choice of language and a yellow arrow ("next") button in the middle and "Emergency" call button at the bottom. And in the top right hand corner are the usual signal strength and battery icons.
When I press the yellow button, I'm asked to connect to a Wi-Fi network. I haven't proceeded beyond that point, as I don't want to mess up my phone even further. Basically it looks like my Moto G3 returned to factory settings and wants me to set it up for first use.
I then tried to reboot the phone a few times. I always get the standard Motorola "stitching" animation and get booted into the described screen. I also went into recovery mode, but almost every single option booted me into the blue screen and one time I got the "No command" screen. But maybe I did something wrong; I'm certainly no expert when it comes to using the bootloader.
Having described all of that, my questions are: is it possible for the phone to have reverted itself to factory settings? If yes - why and how? I have an SD card with a lot of photos, documents and application data that is very important to me. Is it still possible to retrieve the data that was saved on the device?
I would very much appreciate any help with this problem!
Thank you,
Meletel
You can copy the contents of the SDCARD while in TWRP.
1. Put MicroSD card and copy the contents of Internal Storage to microsd though TWRP File manager
2. Connect your phone to your computer by USB Cable while in TWRP and you can access your phone through MTP