I upgraded from a rooted 4.4.2 using muniz instructions last night and using the DeOdexed ROM, and then used his batch DeBloater on Extreme to remove all the crap. The upgrade wiped my phone (not a bad thing, I wanted to start fresh), so I'm at a fresh starting point other than what is mentioned above. Thanks muniz btw, you're awesome.
From here I wanted to turn on Phone encryption, as an extra security measure. Encrypting the external SD card went fine, but encrypting the phone did not... It displayed the little encrypting android screen for a few seconds and then went black, button presses did nothing. After waiting over an hour I pulled the battery and restarted. I got informed that the encryption failed and the phone would be restored to factory default. No biggy, just back where I was an hour ago.
So the question is, before I try this all over again, does the encryption work with this custom ROM and debloated? Is there anything special I can do or might be doing wrong? And will this interfere with root or anything else I may want to install in the future?
Does anyone use the built in encryption with their android?
BeanBagKing said:
Does anyone use the built in encryption with their android?
Click to expand...
Click to collapse
You need to disable superuser, reboot phone, enable the encryption and then re-root. I did this and everything was working fine until one of my kids entered my pin wrong a few times in a row and the phone did a factory reset... I upgraded to OC1 rather than go through all the trouble again.
Related
Hello.
My device is encrypted by CM10.1 (15.7.13)
Since then the cm-updates dont work. (mounting-problems)
I like to undo the encryption, but factory reset dont work too. The encryption and data is still on the device.
The Encryption-Button in the menu is without function.
Restore abortes because of Mounting-Problems.
What do I have to do?
Samsung note2 with cm10.1 can't get rid of encryption
I'm having the same issue. even after using TWRP to format the drive (which states that it will remove encryption) -after installing a new rom, it asks me for the encryption password, which, no matter which password I use (even the one the drive was originally encrypted with) doesn't work.
Petrosilius Zwackelmann said:
Hello.
My device is encrypted by CM10.1 (15.7.13)
Since then the cm-updates dont work. (mounting-problems)
I like to undo the encryption, but factory reset dont work too. The encryption and data is still on the device.
The Encryption-Button in the menu is without function.
Restore abortes because of Mounting-Problems.
What do I have to do?
Click to expand...
Click to collapse
Had the same dilemma myself a few months ago.... I flashed my phone using Odin with the latest samsung rom and then I had to factory reset it again after flashing to remove the encryption completely. And I had a few issues during flashing which scared the **** out of me
here is my thread: http://forum.xda-developers.com/showthread.php?t=2185837
I was using paranoid android rom
From what I understood only the Signed recovery's (original stock ones) can remove the encryption.
My advice google around before doing anything, because nobody wants sudden heart attacks when things go wrong.
I hope you can fix your device without issues.
phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues
All the lock screen options but pin and password are grayed out. The phone won't even let me lock it with a pin or password, it automatically goes back to swipe. They have a message under them that says "disabled by administrator, encryption policy, or credential storage". I've googled and I already cleared all credentials, unchecked everything under device administrators, and made sure SD card and phone encryption was turned off. I also wiped the cache and dalvik cache just to see if it works. The sim card lock is also off. Any advice? I'm stumped
Thanks
Edit: Fixed by flashing a new ROM. This thread can be closed - thanks
Keekers said:
All the lock screen options but pin and password are grayed out. The phone won't even let me lock it with a pin or password, it automatically goes back to swipe. They have a message under them that says "disabled by administrator, encryption policy, or credential storage". I've googled and I already cleared all credentials, unchecked everything under device administrators, and made sure SD card and phone encryption was turned off. I also wiped the cache and dalvik cache just to see if it works. The sim card lock is also off. Any advice? I'm stumped
Thanks
Edit: Fixed by flashing a new ROM. This thread can be closed - thanks
Click to expand...
Click to collapse
I've got the same problem.. but have removed root by reinstalling the stock rom. I've reflashed the stock rom twice through ODIN without any luck. What ROM did you use? Any tips?
GuySmiles said:
I've got the same problem.. but have removed root by reinstalling the stock rom. I've reflashed the stock rom twice through ODIN without any luck. What ROM did you use? Any tips?
Click to expand...
Click to collapse
Is everything else back to stock and acting normal? I am using the ECHOE ROM. That would be such a bummer if you have to reroot to fix the lock options. Did you encrypt and then decrypt just to flip it on and off again?
There are threads containing the changes you have to make to your build prop. Surge1223 had a zip I think to flash.
Not 100% sure but it was like an ro.secure line you had to change.
We had this issue before towelroot using prerooted roms.
Sent from my Verizon NC5 Galaxy S4 w/ GEL and Xposed
Keekers said:
Is everything else back to stock and acting normal? I am using the ECHOE ROM. That would be such a bummer if you have to reroot to fix the lock options. Did you encrypt and then decrypt just to flip it on and off again?
Click to expand...
Click to collapse
I found a fix, as strange as it is. I installed stock ROM NC1 (4.4) first, which finally worked well on my phone and then flashed NE1 (4.4). My knox is showing nothing, so looks like all is well.
I have no idea why I had to flash the original 4.4 before the newer one. Hope this can help someone else as well.
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
gilbnx said:
Hi,
Last night I installed the new stock lollipop. Initially I had a problem with rooting it but eventually everything was working fine. I've used Philz recovery and cf-auto-root. All seemed fine, and I've got all my apps, accounts, etc. back.
This morning I woke up and it looks as if at 6:02am the phone just froze. The strange things are (1) I could turn on and off the display so it was not completely frozen, just the UI (displaying new screens and receiving a response from the keys or the touch screen). (2) I thought to reboot into recovery and when I did - it was the stock recovery! not sure what happened to Philz that was there before?
In any case, I did clear cache and restarted. The logo came up but after 20 sec I've got "unfortunately, media storage has stopped". Of course - it did not receive any response from keys or the touch screen so I could not release this message - only on-off worked. After a minute or so, I saw that other services are crashing...
Of course I can do yet another "wipe to factory" but I was wondering if anyone experience the same. If I will make it work after clear to factory - I'm afraid it will behave the same after a day or so... Any suggestions?
Thanks!
Click to expand...
Click to collapse
This happened to me. I had to do a factory reset.
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
elesbb said:
I seriously do not recommend cf auto root(because its not designed for this firmware). Use chainfire's update SU zip that you flash through a recovery. That update SU zip will prevent the stock recovery from being re-flashed. In addition, I always do a factory reset (wipe entire internal storage) before updating the ROM since I root. If I didn't root or anything, I wouldn't wipe my data. But when we root and mess with stuff, plus all the tries to prevent root, it conflicts sometimes. So a factory reset is always best. I was able to use Titanium Backup to restore everything. Just forgot to backup my Internal SD card.. xD
Click to expand...
Click to collapse
Thanks elesbb, I saw your message just now but I have my phone working already since few hours ago after a 2nd stock reflashing. If I have the same issues as before - I will use chainfire's update SU.
What I did find is that once I enable accessibility (to apps like Tasker, and an LG bluetooth headphone I have (so it could announce notifications) the phone becomes unstable; it just went through 2 boot loops but eventually recovered... Hopefully it will stay stable.
Gil.