Rooted with CF-Autoroot, now encryption not possible anymore - Galaxy S 4 Q&A, Help & Troubleshooting

I just rooted a brand new Galaxy S4 on i9505xxuemke
Before I encrypted and decrypted several times. Always worked great. Now after root when it should encrypt display shows shortly the green android and then it goes black. Device does not react anymore. After about 1 minute it vibrates and reboots. However I don't have to enter my password to boot. Only to unlock. Now I can go to options and try encrpyting again. Hower same behaviour as before. Any suggestions?
There are no apps installed, no google account and so on. Its factory fresh. I even restored factory settings. Same behaviour.
Any ideas?

Related

[Q] Unable to boot after encryption

Hi everyone,
I enabled the encryption on my unrooted unlocked G2. Once the encryption was done, it rebooted and asked for the pin to boot. In entered the pin but the phone keeps rebooting and asking for the pin again and again.
I have tried more than 20 times, sometimes it boots to android but it shows a warning sign in notification (backup account needed) and then reboots after a few seconds. I tried turning on/off but the same thing happens again.
Is there anyway I can get my data out of this mess before doing a factory reset? Maybe rooting it from download mode and mounting from recovery?
Thanks a lot!

i9505 encryption failed

hi, i flashed a custom rom yesterday (http://forum.xda-developers.com/show....php?t=2794546) the super slim version.
everything worked fine. wanted to encrypt the device, charged it and pressed start encryption. it showed me the green android guy for a second, then rebooted. i went to sleep. today i see its giving me 3 notification on the screen: settings has stopped, interface stopped, and telephone stopped. i can press ok, then the screen either goes blank and nothing happens but the notifications pop up again after some time, or it reboots and does the same. i can still get into recovery, but /sdcard is inaccessible. should i flash from the external sdcard?
should i flash something with odin? i just want it back working. thanks

T365 device encryption doesn work

Hi!
I have a problem. The device encryption (Settings - Security - Encrypt device) does not work for me.
I'm on stock T365XXU1AOA3 (SER) firmare (no root or other mods, pure stock).
After tapping 'encrypt device' and entering password and plugging in a charger, 'black screen with green android' appears for some time (~5 min or so) and then it reboots.
After rebooting it becomes obvious, that device is still not encrypted yet.
What is the problem?
andreya108 said:
Hi!
I have a problem. The device encryption (Settings - Security - Encrypt device) does not work for me.
I'm on stock T365XXU1AOA3 (SER) firmare (no root or other mods, pure stock).
After tapping 'encrypt device' and entering password and plugging in a charger, 'black screen with green android' appears for some time (~5 min or so) and then it reboots.
After rebooting it becomes obvious, that device is still not encrypted yet.
What is the problem?
Click to expand...
Click to collapse
i dont know, never tried that encryption, did you try on a fresh installation? else you can do a factory reset before.
pls tell me if it works so we can test twrp encryption.
I do not understand something, but after reflashing everything it become working.
So I was able to encrypt device and decrypt on stock kernel/rom.
But if I change kernel to custom, which I complied by myself, decryption stops working.
There are messages in logcat from SecureStorageDaemon that it stopped working because kernel is changed.
How can we test twrp encryption?

Full Disk Encryption hangs for hours on rooted SM-910C

update, read at the bottom.
Hi, I have a Samsung Galaxy Note 4 SM-910C which I have rooted after flashing a stock Samsung rom. If I recall correctly, I flashed a stock android 4 rom trough ODIN, did it a CF-Auto-Root and eventually updated android 5 through wifi (OTA). SuperSU was installed.
I have attempted to do a native full-disk encryption trough the default Security menu; the phone went into a black screen with a green outline android robot in the center, with no progress bar or text of any kind (I found the image online, but can't post it due to account lack of privilege) . It has been on this same screen for over 8 hours now.
The device was NOT in USB-debugging mode.
What are your suggestions? Should I try some kind of reset? Is it possible the process will resume and is taking so long due to the amount of files? Or I shouldn't expect it to work since I tried encrypting a rooted device?
I'm not worried about any files in it, but I'd like to make sure to be able to recover the phone without bricking it. I'll be leaving the phone plugged to the outlet and untouched for the foreseeable future...
Thank you very much.
UPDATE: I powered off the device (had to remove the battery) and when turned it on again was met with the "Encryption unsuccessful" screen. Then I turned it off and went into recovery mode by pressing and holding POWER+VOLUME UP+HOME. Even tough it displayed a warning - dm-verity verification failed - I chose wipe/factory reset and then rebooted the system and it seems to have worked fine. After the start splash screen and a notification that is was installing applications (bloatware), it brought me the Welcome to Samsung Galaxy configuration wizard.

Restart directly after unlock pattern

Hello everybody,
two days ago, my Mi A1 just spontaniously restarted while running.
But since then it is stuck in the "Android one" screen. With multiple restarts, I finally manage to get to the unlock screen.
If I then enter my pattern the screen changes to "Android is starting", but after two seconds the phone restarts again until I'm at the "Android one" screen again.
So I can't enter the actual system.
I can enter the stock bootloader and also fastboot, but I'm not entirely sure what I can do there (except a factory reset).
I also tried to enter the failsafe mode (by hitting the shutdown icon longer in the unlock screen), but the phone just normally restarts as mentioned early. I don't seem to get into that mode.
My suspicion:
For a few months I'm running out of disk space. Because of that I couldn't install all the big updates lately. I suspect, that the OS somehow forced an update that failed because of the space issue. At least this is the only thing that I notice lately what could explain the situation.
Do I have other options to resolve my problem, except a factory reset?
My last backup is two months old, so I would survive deleting everything, but it would be way better if I don't have to
Do you guys have any hints for me?
regards and thanks in advance,
koala
I was getting nervous and just did the factory reset.
And it seems to have worked just fine.
Some data is lost though.

Categories

Resources