I have a Sprint Samsung Galaxy S4 (SPH-L720). My device is currently stock rooted running Android 4.4.2. I recently just did a factory reset and need to encrypt my device. I have my screen lock password setup and when I select to encrypt the device it shows the screen with the android gear icon for a second then shuts off. About a minute later it will turn on again on its own and boot right up to the regular lock screen. It will not encrypt and gives no error message.
The only references I have found on a Google search about encryption not working was referring to an error message saying the encryption failed and asking the user to factory reset.
Any idea what is causing my issue?
Still having this issue. Even reflashed again and it's doing the same.
Related
Hi,
I did a bunch of search strings on here and Google to try and find a solution to my problem to no avail. I really hope you guys can help.
My device: Galaxy Note 3 - N900W8 - Rooted and Unlocked (RegionLock Away 1.3)
My Problem:
I'm trying to connect the device to my works account via Exchange ActiveSync. My company forces encryption on the device as part of the setup processes. When I try to Encrypt the device (Fast Encrypt or not) it shows the Encryption Android dude (Green) as if it's going to start and then the phone just turns off and reboots.
Any ideas what the issue could be? Is it possible that because the phone is rooted, the security settings that my works places on it doesn't like it?
Thanks.
H
Hi, I was experiencing the same thing, I was playing with the encryption and now my lock screen pattern and pin is not an option anymore and I have to use the encryption password, when my device is not even encrypted! I cannot decrypt because every time I go into the Encrypt device option, It goes back to rebooting just like you mention. Anybody can help?
Thanks,
T2
Hello,
I have recently rooted my Galaxy S3 and today I tried to encrypt it in order to get access to my Exchange account (requires encrypted device). When I select encrypt device from the settings menu, I get very briefly the Android picture (with its guts open) but after one or two seconds, the screen goes blank, the phone restarts and it is not encrypted.
I have rooted my phone using the CF mod and ODIN.
If anyone has any suggestions please let me know.
P.S. The S3 is running Android 4.3.
Thanks
Hi,
i've encountered the same issue. The fix however is quite simple. Boot into recovery and then select "wipe data". After that, you can encrypt without any problems. But keep in mind that all your data will be lost, better make a backup before
Cheers
trivial1 said:
Hello,
I have recently rooted my Galaxy S3 and today I tried to encrypt it in order to get access to my Exchange account (requires encrypted device). When I select encrypt device from the settings menu, I get very briefly the Android picture (with its guts open) but after one or two seconds, the screen goes blank, the phone restarts and it is not encrypted.
I have rooted my phone using the CF mod and ODIN.
If anyone has any suggestions please let me know.
P.S. The S3 is running Android 4.3.
Thanks
Click to expand...
Click to collapse
I've tried to wipe data/reset the device, but the problem remains on my GS3.
Hey guys!
My S4 is stock 4.2, but rooted, VRUEMK2 build, for reference.
I need to encrypt my device to use my corporate email, however, it keeps failing. Basically, to go step by step, I set up a PIN screen lock, connect my charger, input my PIN, and hit encrypt... I see the green Android dude for about 10-20 seconds, my phone reboots, and I'm back at my lock screen. No encryption applied.
I've done around three to four factory resets and it still doesn't work.
Any advice?
I bought this phone which was freezing up. I thought that a firmware upgrade would do the trick. However, there was a Samsung Account of the phone and I was not aware of. The phone goes to the first set up screen, asks me to connect to WIFI but there is not WIFI providers to choose from. I click in the refresh WIFI list and the phone asks me to turn on WIFI. However, I do not have access to the WIFI on/off switch due to Samsung account lock. After a couple minutes the phone would again freeze up. Sometimes it restarts or it would simply stay in a black screen. I have to remove the battery and start the process all over. I have tried re-flashing via ODIN . I update the phone via Verizon Software Assistance to the latest firmware Marshmallow G900VVRU2DPF4. But I downgraded to G900VVRU2BOE1 Lollipop 5.0 firmware now. I also tried removing the account by flashing the modem.bin file but I get stock in the same spot. Guys, please help!
Samsung A8 (2018), (SM-A530F/DS) homescreen stuck in "phone is starting" after update
Hi guys, yesterday i did a software update for my samsung A8 (2018) phone and it was going normal until i received an error message at the end of the update. My phone continued to boot successfully but now the homescreen is always stuck in "phone is starting" message.
The phone itself works and i am able to open other apps via google playstore but the homescreen is unusable. I have tried doing cache partition wipes and factory resets, i also thought it was a soft-brick so i tried FRP hijacker with the soft-brick fixer but it just says "check connection" even though my PC successfully scanned the port of my phone. When i open my phone in recovery mode it says "firmware is not valid" at the end of the command line.
I have tried searching online for similar issues but most users have experienced bootloops which is not exactly the problem i have right now.
Any help would be greatly appreciated, thanks
@Verthingale
Taken from Samsung:
Devices with Android 9 or higher will automatically enable file-based encryption if it has a PIN, pattern, or password set up. During the boot process, the phone will display "Phone is starting..." and the screen may be blank for a few seconds while encryption is taking place. However, if you feel it takes too long for your phone to start, you can disable the encryption to cut a few seconds off of the boot time.
Click to expand...
Click to collapse
jwoegerbauer said:
@Verthingale
Hi jwoegerbauer, thank you for the reply however unfortunately i don't think the "phone is starting" protocol is actually working. I only experienced this problem right after the latest software update and that was about last night, I have actually tried waiting for the phone to load up but it actually never does (even though i left my phone idle and waited for hours). I am fairly certain that it is a glitch/bug caused by the error at the end of the software update however i am not sure on what to do in such an occasion.
So as to clarify, the software update DID NOT complete as there was an error/failed message right at the end of it but while looking up in the internet i found out that apparently software updates are permanent and cannot be reverted back?
If that is the case then i am really in a pinch right now as i cannot go back to my old software version and yet the new one also does not work.
Click to expand...
Click to collapse