i have a galaxy s3 t mobile phone and it is encrypted. today i rebooted it and it didn't ask me for my password to the encryption... so i went to settings and security and it says that its encrypted...rebooted again still didn't ask for password. the phone just boots up as normal and works. i even rebooted into twrp and it didn't ask me for the password to my storage... im going to be wiping phone and trying to get encryption back...is there some way to decrypt the phone that my butt could have done?lol
Related
Hi, thanks for reading and helping, I would really appreciate that if you helped me.
I've got a Samsung galaxy tab 3 model SM210.
I have to tell you that I have set a memory encryption on that device in addition to the lock screen password.
The encryption uses the same password as the lock screen uses, just when I reboot the device. Without decrypting the device, you won't be able to fully load the OS.
I'm telling you this because I have a feeling that this is the source for the problem I have.
The OS felt really slow and I wanted to upgrade. I had 4.1.2.
I have downloaded version 4.2 jelly bean and installed TWRP recovery using Odin.
Then I have installed the root kit and the jellybean.
After rebooting, I noticed that that all data and apps were still there and I have had a problem turning on the wifi from 'settings', it crashed every time.
I loaded back the TWRP and formatted the device.
The installed again the jellybean.
Since then, the device is asking me to enter decryption code (the same one from before).
I wonder why this message still appear after formatting the whole device?
Anyway, I enter the code and then the android logo appears and stuck there.
I have tried multiple times to reinstall an format etc.
every time I get to this place.
How do I fix this?
EDIT:
more bad news.
TWRP has stopped working, even after relfashing it with Odin.
I have installed CWM and succeeded installing StockRom V2.0 (not the samsung stock rom, its name is "stockrom v2.0) and after that the OS loaded up and I have got the screen which asks me to enter the code for decryption.
The code was "l1212", it does not work anymore. How can I bypass this screen?
I also installed right now the first rom I have told about above, the jelly bean, then the decryption screen comes up and the code above is ACCEPTED and then stuck again on the Android logo...
What a nightmare.
I think the onlyst what help, is flash Org. Stockrom with Odin. Flash a Custom recovery and root you Tab, after that make a backup.
I now since a lot of month ago a other user has done the same.
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
jtguf87 said:
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
Click to expand...
Click to collapse
I am having the same problem. Unfortunately, I have not gotten any answer. Sorry I couldn't help, but at least we're not alone.
same here, have had same issue with multiple dailies. do you think this is with twrp or cm12?
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Shakinghead said:
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Click to expand...
Click to collapse
How did you do it? I've tried to encrypt with 27/08/2015 nightly and I couldn't. It said encryption failed and I had to wipe it.
I'm using the 26/08 (UK date format) build - This is the one that broke Chrome. I just encrypted the phone using the settings. I've been trying every couple of weeks for sometime. In the past I get the CM logo and nothing happens. If I remove the battery then the phone boots OK...so clearly the encryption hadn't started. This time I left it and walked away. 30 mins later I went back to the phone and it was prompting for the encryption password after boot....So all good for me....except TWRP cannot decrypt the encrypted partitions...
I am using the D855 model.
I'm having similar issues. I was able to encrypt after installing the Resurrection Remix v5.5.5 but now TWRP shows internal storage as 0mb and throws out a bunch of mount errors. So can't backup or load anything new through TWRP now.
The only way I was able to change ROMs was to flash the stock ROM through the LG flashtool, thereby unrooting the phone and then starting the whole process from scratch. It's a big pain because everytime I do that I need to get admin approval to setup my work email and then need to encrypt again , which locks me into the existing ROM again!
Ughh!! Can't wait for a solution top this problem.
Happens with Fulmics only.
I used this phone with fulmics for a year or longer.
Recently I flashed this rom https://forum.xda-developers.com/lg-g3/orig-development/rom-pixel-g3-aosp-t3571499/page70
I then encrypted the phone. I don't recall entering a pin or being asked for a password. The phone showed as encrypted.
I then attempted to flash Fulmics again but got
"enter password to unlock 30 attempts remaining" screen.
I reflashed the pixel g3 ROM again successfully. Phone shows as unencrypted and boots.
Why did this happen?
Do I need to do anything prior to flashing a different ROM?
I did format, reset, wipe, etc
I use a Linux computer so it'd be useful to use Linux tools if needed, but I could also get to a windows computer if necessary.
it was an ebay refurbished phone with stock rom unencrypted. I then flashed fulmics and used it for a long time. I never encrypted and was never asked for passwords.
Having some serious trouble. I rebooted my phone and it asked for my password once it was done as always but this time it said it was wrong. I'm certain I used the correct password but even tried my other alternatives to be sure and still a no go. This isn't the decryption option password you get when booting but my lockscreen password. I booted into recovery and it asks me for an encryption password that I never set but I know this is a common issue with twrp. Tried to go back into android but wouldn't let me because of the "wrong" password so I used the failsafe and went into recoveries file manager and deleted my lockscreen settings to remove my lockscreen passcode (tried and proven method, done it dozen times before). Got past my lockscreen this time but now it was saying starting android forever. Figured it was something with the passcode being deleted so I just decidd to factory reset from the recovery and take that loss. NOW the problem is upon booting the rom in trying to start the setup, I'm stuck on the "just a sec..." screen that comes up after you click start. What do I do from here? I cant access anything in recovery because the encryption passcode issue so I'm kind of stuck. Also I'm a work right now and we cant connect our phones (or any USB for that matter) to the computers and laptops because theyre government property and on a secured line. Any help PLEASE, Ill be home later and can try more then.
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
loeffler23 said:
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
Click to expand...
Click to collapse
Hey, I got my phone back working after that and rooted again and flashed same rom. NOW another problem, I rebooted my phone and its not accepting my PIN anymore, nor my fingerprint, and I cant reset through TWRP because of encryption. WTF is the issue, how do I fix this or do I have to flash-all again?
Okay so my device aint a redmi 7 but its a y3 so its basically the same and everything made for the 7 works on it just fine, but this odd encryption issue is very frustrating, my device keeps on getting encrypted during boot and I can't unlock it at all, even if there was no security set on device it wants a password, I can't seem to fix this at all, the first boot is fine on any custom rom but on the 2nd or 3rd it automatically gets encrypted, even on backups, if I restore a previous backup it wants encryption code if that doesn't appear and the phone boots up fine but when the lock screen appears, the previous screen lock password doesn't seem to work. What am I doing wrong here? Even in case of backing up using twrp? This encryption thing is really frustrating!
Thank you!
try different locking methods when setting up the ROM for the first time
a safe haven said:
Okay so my device aint a redmi 7 but its a y3 so its basically the same and everything made for the 7 works on it just fine, but this odd encryption issue is very frustrating, my device keeps on getting encrypted during boot and I can't unlock it at all, even if there was no security set on device it wants a password, I can't seem to fix this at all, the first boot is fine on any custom rom but on the 2nd or 3rd it automatically gets encrypted, even on backups, if I restore a previous backup it wants encryption code if that doesn't appear and the phone boots up fine but when the lock screen appears, the previous screen lock password doesn't seem to work. What am I doing wrong here? Even in case of backing up using twrp? This encryption thing is really frustrating!
Thank you!
Click to expand...
Click to collapse
If you can unlock the device try goin to settings and turn on developer options and head towards last option in developer options i.e Encrypt data using screen lock open it and turn off it