Develop Bugs

[Q] CM10 m2 Encryption Issue

Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?

fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app

[Q] Encryption is Broken on Rooted Galaxy S III

Hi, I've tried to search for info on this but most of the relevant things I find were pre-4.3, pre-KNOX, I don't want to ruin something so I'm going to post.
I would like to root and have encryption working, but since I rooted, the phone will not encrypt. I had tried to root after encrypting the phone, maybe that messed something up.
Here is exactly what I did:
-Got the OTA update to 4.3
-Turned on full device encryption. it worked fine.
-I then realized you have to use the same passcode for encryption and screen unlock which is a pain. Found an app which purports to allow you to use separate passwords for these: Cryptfs Password
-Requires root access.
-Ok, so I root the phone using Odin 3.07, CF auto root. (CF-Auto-Root-d2spr-d2spr-sphl710)
-Success in Odin, Reboot phone, enter my encryption password
-It hangs at this screen indefinitely: (forum won't let me link picture.... black background, green android robot split in half like gears/puzzle, no text)
-I can no longer use phone, so I do hard factory reset to remove encryption, phone boots up
-Now I update SuperSu in play store and it disables KNOX popups; root checker says root successful.
-So now I have a rooted phone, but no encryption.
-I try to re-encrypt phone.
-When I hit "encrypt", I get that same android robot screen for 30 seconds then phone reboots like nothing happened, asks for passcode. Obviously encryption didn't work.
????
What steps should I take so that phone is both rooted and can use encryption?

Tried some more things:
-Flashed the phone with the factory 4.3 ROM, MK3 everything...
-Now encryption worked again.
-I do a factory reset to remove encryption.
-This time I root with a different method: flash philz touch recovery, "DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0", "UPDATE-SuperSU-v1.86"
-root checker says everything is successful
-I try to encrypt and it hangs at that screen with the android robot who is split in half, for 30 seconds, then phone reboots
Am I missing something?
Does rooting + 4.3 + encryption not work together?

Jessooca said:
Restore your phone to stock with Odin and the latest tar file.
Root your phone with CF Auto Root in Odin, be sure to enable usb debugging mode first.
After it's rebooted open supersu and it should ask you if want to disable Knox, select yes and change your supersu to grant and you can do whatever you're trying to do.
It seems as if Knox is keeping you from doing anything encryption wise as it's doing it's job protecting the security features of your phone.
After you've done all this, let me know.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Thanks so much for the reply, appreciate the help.
However, before I saw your post, I kept tinkering with different combinations of rooting and encrypting and I fixed it.
Here is what I did.
-Started fresh with stock 4.3 recovery/rom
-encrypted
-rooted with "saferoot", it was a .bat that I ran while the phone was on
-no problems encrypting or decrypting anymore
Now that I had root access, I could use the apps that allow you to change the encryption password independent of screen lock.

Stuck on Startup

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?

Bootloop after disabling settings app. S20

I got into a bootloop after disabling the settings app from the terminal emulator, using the command pm disable, am rooted using magisk. Now it is telling me to enter safe mode, but the safe mode is completely unusable. Anyone can tell how to undo so it boots up normally, besides factory reset

Bummer. If nothing works you could go to recovery and wipe phone clean from there. You'll need to look up the button combo to go to recovery, don't recall myself.

Can't believe you decided to proceed even people told you your device will brick. Nothing you can do other than factory reset your device from recovery. You also can flash ROM via odin. Next time listen to others. Otherwise, don't even ask in the first place

twinh3ad said:
Can't believe you decided to proceed even people told you your device will brick. Nothing you can do other than factory reset your device from recovery. You also can flash ROM via odin. Next time listen to others. Otherwise, don't even ask in the first place
Click to expand...
Click to collapse
Actually my phone was working just fine while the app was disabled ,but I forgot to to enable it again before reebooting my phone , simple mistake

tab s4 bootlooping

I know that there are many threads already about the tab s4 and other devices bootlooping but every in thread I saw the device also shows an error of some sorts or you can enter the recovery mode.
In my case it is a bit different, as I think it was caused by me being stupid and accidentaly deleting something I needed to boot with the universal android debloater. I deleted one partition that had no discription but seemed save to me but oh well. After deleting the package with UAD I used it for a while and the only reason I restarted it is because some app (i think overdrop) had a notification that I need to turn of battery optimisation for it and restart my tablet. So I did that today in the morning and in the beginning everything looked fine. I wondered why the Samsung logo was on the screen for so long but decided to let it do its thing. Then there was a menu that said something about it not being able to boot and told me what to do in 3 Steps: 1: retry the boot process (which just brought me back to the same menu); 2: reset the app data/cache (which seemed more promising) 3: contact support (which i didnt do because i feel like they would just tell me that they cant help me with that because its a device from 2018 and i used an "illegal" tool). So i reset the app data/cache and then tried to boot it up again. Then it bootlooped and I went into recovery mode and tried to hard reset the tablet hoping that the missing package would be restored with the factory reset but thats not a thing appearently.
So the things ive tried to solve this issue are:
using adb/aud to restore the missing package (didnt work because despite some thread saying that adb can be accessed while bootlooping I couldnt so that isnt gonna work)
Force shutdown and boot into recovery to look at the log and find something (I cant even get to the recoverymode anymore because the keycombination would just "restart" the booting process)
Sorry if my english isnt understandable, it isnt my first language