Develop Bugs

[Q] Device Encryption Failed - Can't Use Phone

Hi folks,
For some stupid reason, I tried to encrypt my phone from within TouchWiz Security Settings. I entered a password for the encryption, and as soon as I clicked start, the process stopped and an error saying "com.android.systemui has stopped" has appeared. If I click OK it pops up again. Restarting the phone gives the same error, and I can't actually use the phone at all, as the error message keeps popping up even if I try to enter the correct password.
I tried reflashing the rom, wiping data, cache and so on, and the same error message pops up as soon as TouchWiz loads up. I don't know how to transfer another rom from my computer to the phone from within CWM (I don't see my phone's storage from within windows).
I thought I'd do a complete unroot, but the stock firmware available for this device is older than 4.4 (which is what I have because I'm using Enewman's SRx 4.0). Everywhere I read it says "DO NOT DOWNGRADE".
I'm not sure what to do, and I have very limited expertise in this matter.
Thank you for all your help folks!

Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?

audit13 said:
Were you rooted with cwm when you to encrypt? I did this with my s3. I was fortunate that process failed but I was still able to boot the phone.
Since you have cwm, did you try formatting the system before installing a new rom?
Click to expand...
Click to collapse
Yep, I was rooted and using CWM. The phone still boots to TouchWiz, but then the error comes up and I can't use the phone at all. I tried formatting the system before installing a new rom too...

So I used adb to sideload CyanogenMod, and flashed it. That seems to have helped the problem

So the in call volume in AOSP ROMs (tries carbon, quantum, cm11) is way too high. Tried reflashing any other kitkat based touchwiz ROM but immediately upon first boot I get prompted to insert the encryption password. When I do, it asks it again. Is there any way to somehow get a touchwiz ROM to work on my phone now? I alwaya do clean installs. Thanks guys

It is my understanding that encryption requires stock recovery.
What bootloader is on your phone?

Looks like I'm on the UCUFNE4. every touchwiz ROM I install asks for decryption, and all the other ROMs are installing OK..

Have you tried using Odin to flash a stock ATT KK ROM?
Edit: nevermind, looks like there is no 4.4.2 ATT ROM on sammobile.com. I assume you already tried wiping cache, dalvik, and data.

Yes I have tried to wipe everything. Even internal storage. So then I had to sideload a ROM using adb. I really appreciate your input!

It sounds to me like the data portion is still encrypted. Were you able to use fastboot commands to erase cache, data, and system before flashing a new ROM?

Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?

tequilaboom said:
Well I used TWRP to erase data, cache and dalvik and system. Would that be equivalent to fastboot?
Click to expand...
Click to collapse
It might be but I have never compared the two methods.
Are you able to issue fastboot commands to your phone?

I have never done fastboot but I could try using it. What should I do with fastboot?

tequilaboom said:
I have never done fastboot but I could try using it. What should I do with fastboot?
Click to expand...
Click to collapse
Boot the phone into download mode, connect the phone to the computer via USD, let it install the Samsung drivers. You will also need the necessary ADB/fastboot files from here: http://dottech.org/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Boot to an command prompt in Win7 or Win8. Navigate to the directory where you installed the ADB/fastboot files and type this: fastboot devices and press enter. Hopefully, your device will appear.

OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?

tequilaboom said:
OK, and once I'm in fastboot, by formatting the data partition, and attempting to install a TW rom, you think it'll fix the problem? Is there something else I have to do in fastboot (what is the sequence of commands?)?
Click to expand...
Click to collapse
Here's a good guide:
http://forum.xda-developers.com/showthread.php?t=2225405

alright I followed the guide, but still no effect

Did the fastboot commands work?
Did you try erasing the userdata partition? Did you try formatting the userdata partition?

I apologize, I should have said that I had no success even after trying to follow the guide. I attempted to use fastboot but when trying to detect my device, nothing showed up in that command window. ADB works no problem (detects device). Again after several tries of formatting the data partition (and everything else), every touchwiz rom asks for the encryption password. However, now when I enter it, the green android with gear appears, and then the device restarts. touchwiz now asks for the decryption password once again....

So typing fastboot devices didn't list anything? Were you in download mode?

Error «Encryption was interrupted and cannot be complete»

Hi Guys! I have a problem, and i really don't know how can i fix it.
My phone boots normally, but when boot finish this error appear in the screen:
«Encryption was interrupted and can't be completed. Phone data cannot be used anymore.
To continue using your phone, you must restore factory settings. After the restoration, you can restore data backed up in your Google Account to your phone»
There is a "Reset Phone" button but if i push it nothing happen.
I have tried to clear data/cache in recovery but nothing changed, I have tried to install a new ROM (i tried a lot of ROMS) but when it arrive to 50% more or less installation fails.
I have tried this guide oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ but it cannot work (Image Attachment)
Also FASTBOOT can't work. (For exemple: if i try to flash recovery it fails remote: failed to flash recovery / erase userdata / cache)
I really don't know where can i also looking
Help me please!

Anyone?

I'm having the same problem....
Restoring an old backup woth TWRP results in the same error.....

hi guys this happened to me too,
luckily I had twrp 2.8.6.0 flashed for recovery.
think you should still be able to get into fastboot if you do a battery pull
then poweron with the powerbutton and volume up till you see the oppo man icon.
then you should be able to flash your recovery with the latest twrp.
if you seen the penquin then this may not work for you. As i have not done a hard recovery before so i dont know if it would work.
I saw the oppo man so i was able to fix it by:
booting into twrp recovery,
i selected wipe --> advanced and there was an additional option to do a wipe for encrypted volumes and i selected all partitions to be wiped
then i installed i had downloaded on my SD card, it was ColorOS 2.0.8i i believed and it fixed it.
sorry if i am a bit grey about the details i did it a while ago so.
Actually found this in the cm12.1 nighlies thread
http://forum.xda-developers.com/showpost.php?p=58304054&postcount=14
issue is possibly due to unified partitions

Encryption fails??

Hi
Anyone have an idea, why after installing a custom rom eg. blispop/excodus or whatever, after flasjing and booting the first time (whit or whitout gapps) i get a encryption fail . saying this was interrupted and not done....try factory resetting (button at middle off screen, says reset) and doing so don´t change anything, manual wiping also changes nothing...??
I´ve never seen this prompt before and not sure what it exactly means?
It happens after flashing cos official 2.14, with twrp 2.8.7.2 , all flashed just fine and working...in cos.
Flashing custom roms gives no errors and seems fine, it boots to the point where this encryption thing shows up?
Tried fastboot oem unlock, which adb says went ok, but no changes whit this error!
Oh and i merged internal sd when i was in cos 2.14 recovery and it works just fine
thx in advance guy´s

spoonymoon said:
Hi
Anyone have an idea, why after installing a custom rom eg. blispop/excodus or whatever, after flasjing and booting the first time (whit or whitout gapps) i get a encryption fail . saying this was interrupted and not done....try factory resetting (button at middle off screen, says reset) and doing so don´t change anything, manual wiping also changes nothing...??
I´ve never seen this prompt before and not sure what it exactly means?
It happens after flashing cos official 2.14, with twrp 2.8.7.2 , all flashed just fine and working...in cos.
Flashing custom roms gives no errors and seems fine, it boots to the point where this encryption thing shows up?
Tried fastboot oem unlock, which adb says went ok, but no changes whit this error!
Oh and i merged internal sd when i was in cos 2.14 recovery and it works just fine
thx in advance guy´s
Click to expand...
Click to collapse
Had the same issue with CM12 on my Find 7a, eventually had to reflash Oppo's stock recovery which has a SD Mass storage option, toggled this and then the boot was able to complete. I then couldn't use the camera or download as the phone said I had no SD card - corrected by reflashing TWRP and changing to ext3

rniblett said:
Had the same issue with CM12 on my Find 7a, eventually had to reflash Oppo's stock recovery which has a SD Mass storage option, toggled this and then the boot was able to complete. I then couldn't use the camera or download as the phone said I had no SD card - corrected by reflashing TWRP and changing to ext3
Click to expand...
Click to collapse
Thx a lot, but only stock recovery i can find is v1.0 which only has usb mass storage option, been inside this option toggled exit usb mass storage option, but same 0, encryption fails...
do you remember or have a link to recovery you used?
edit:flashed 1.2v and there´s no such option
Thx
Edit again:Lol, after fiddling around with getting non unified storage etc, formatting and flashing sahara tool , i totally forgot about new modem/security update necessary and made by cyanogenmod team, (This will give the encryption fails error else) when flashing nightly with updates all was working great!!
So easiest way to switch between unified/non unified is by installing cos 2.14 and use recovery to chose layout, then flash a cm nightly and all is great.

Format failed when doing a full wiping of OnePlus 3

Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx

cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.

tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.

Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s

Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.

cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.

cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse

What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.

@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.

Stuck in install loop - keeps getting wiped on boot?

I'm trying to install LineageOS 17 on a OnePlus 6.
I can boot into twrp and the install process appears to work successfully. I can swap slots and install into either slot.
When I reboot the phone I get to the screen that says "Start" and "Fastboot mode" at the top. If I try to start the phone it comes back to this screen. When I go back into twrp, the contents of /sdcard is empty. I can copy over files using adb push, install the rom and then reboot. However, every time I reboot it seems like it completely wipes the phone including the install it's just done and /sdcard is also wiped.
When I booted into twrp previously, it required my unlock code. It now no longer does that. I wonder if this is part of the problem?
If I install just oxygenos, it takes me to the oxgenos recovery screen but I cant' do anything from there. I'm guessing that won't allow me to boot with an unlocked bootloader?
Can anyone advise how I can get out of this? Installing anything using twrp looks like it works, but it's like it gets wiped every time I reboot.
I can't even seem to get OxygenOS back to working.
Can anyone give me some tips on where to go from here? Nothing I can do from TWRP seems to help. I have tried wiping everything in both slots and reinstalling oxygen, no luck

Still stuck?