Error «Encryption was interrupted and cannot be complete» - Oppo Find 7 and 7a

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

Related

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.

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

Soft bricked Find 7a

Hello there, hope someone can help me with my problem.
I softbricked my Find 7a while trying to reinstall ColorOS 2.1.5 stable. When I boot the phone up normally, it tells me that "SystemUI has stopped working" and that the Encryption was unsuccesful. no problem, I thought, lets just wipe everything and reinstall it via ColorOS Recovery.
But nothing works there - I can't wipe data, it always tells me I need 250 MB free space - and just reinstalling ColorOS 2.1.5 didn't help - it says the installation was succesful, but when I boot it up, its again "Encryption unsuccesful", just like before. Trying to wipe everything via fastboot didn't help either, (used 'fastboot erase xxx', whereas xxx stands for cache, system, userdate, recovery and so on), I always get the following message: FAILED: (remote: failed to erase partition)
I've also tried the unbrick tool from Irwenzhao but whenever I click on start a green bar is loading but after 5 seconds my phone just reboots, no matter how often I try.
I also have the feeling this has something to do with a failed unification (LVM), because I tried to switch back so it would maybe work... nothing.
Seems like I cant delete anything, even though I can boot up the phone, go into fastboot mode and go into recovery mode (which was useless so far since nothing works here)
Am I missing something here? Would be great If someone could help me out here..
Do you have LVM installed before per script? Try uninstalling it (Although ColorOS should work with LVM): http://community.oppo.com/en/forum.php?mod=viewthread&tid=46285
Or try this: https://www.youtube.com/watch?v=-HraWDrHve8

Mi Max 3 6/128 SoftBrick - What to Do?

Hello,
I have a Mi Max 3 6GB/128GB which I got from the UK which arrived unlocked and with Global Stable ROM installed which actually updated to V10.3.3.0.PEDMIXM by OTA - I tested.
fastboot getvar anti shows failed, so I assume no Anti Rollback Protection, which I thought a little strange, it being MIUI 10 with (after OTA) June 2019 security patch.
I spent the last couple weeks setting up the phone to my liking (I have 300 apps installed) and finally finished yesterday.
Then I wanted to uninstall some Google/Facebook/Xiaomi bloatware using the excellent "Xiaomi ADB/Fastboot Tools".
I was pretty careful in my opinion to only remove the safe ones (the tool claims to only show you the safe ones) like Music, Video, MiPay, MiCloud, MiForum, MiSIM and all Facebook in the ADB section of the tool.
The I switched in fastboot and thought it would be a good idea to wipe Cache (nothing else).
Upon restart the Mi Max 3 first shows the black boot screen with unlock written at the bottom, then changes to the normal boot boot screen with MIU and the points at the bottom showing that it is busy booting. It stayed there for a while and I thought maybe it was rebuilding the cache and it took that long, but after 30 min still no luck.
Then I fired up the "Xiaomi ADB/Fastboot Tools" on my PC again and it told me the phone was in ADB mode, I could reboot into system mode, where the same thing happened - no progress in booting.
I cannot turn off my phone either, but I can switch from sastem boot (which gets stuck) into fastboot mode via ADB.
Would someone know what's wrong and what I can do to get my phone out of that bootloop while hopefully maintaining all my data and setups, on which I worked for weeks?
Thank you so much for your help!
P.S .: In case it could help: I could read out the phone properties of the Mi Max using the "Xiaomi ADB / Fastboot Tools" while it was softbricked, meaning the ro. init. persist. sys. and dalvik. values of the smartphone. I am happy to post them here, if requested.
Hi,
Do you have an SD card? If so, remove it, because as you cleared the cache, I think it might be a problem with encryption (lost reference).
In your case, I believe a reset will work again, but you will lose application configuration data. Via ADB you can backup files only.
If you do not have unlock bootloader, be very careful as you will not be able to flash TWRP or others.
Good luck!
Thanks, the phone came from the vendor with Global Stable ROM and unlocked. It may be an unofficial unlock, though I was able to install OTAs.
I don't have SDCard.
How can I do ADB backup?
I was able to flash official TWRP just a few minutes but it couldn't access data, maybe because it is encrypted. Now I think I will try and install latest Orange Fox r10 stable, which I think should be able to handle decryption, so that maybe I will be able to get at my date.
Any other advice?
Hi,
Now that you have TWRP, clear cache / dalvik from TWRP and try starting again, maybe start system.
About copy via adb follows a link below:
https://www.lifewire.com/use-minimal-adb-and-fastboot-4582201
in step 2
"
The command to move files from your computer to your phone is adb push.
To move files from your phone to your computer the command is adb pull.
"
Through TWRP you may also be able to back up. Go to (mount partitions) and select all partitions.
Make sure the TWRP MTP option is on, it will allow the device to be mounted via usb on your computer.
I use TWRP I use nijel8, it works very well.
https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
If you can't launch system, you will have to reinstall the Rom.
Good luck!
PS.
More help for adb.
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Thanks for your advice!
I first used the official TWRP and I was able to flash it and start it.
But then the wipe of cache and dalvik failed.
And I could not mount data etc..
When I tried to repair the file system with TWRP I got error 255 - unable to repair data from fsck.f2fs.
Then I saw in your signature that you use nijel8's TWRP and I read that thread, and I started to understand, that my TWRP errors most likely originate from TWRP not being able to decrypt my partitions.
However, towards the end of the thread it seemed that nijel8 stopped working on that project and then Xiaomi once again changed the encryption in MIUI 10/Pie and so it was recommended first to use an obscure Chinese TWRP and then to move on to Orange Fox Recovery Project, which supposedly can handle the decryption better. So that's what I got and I am just about to install it and see if I can rescue or even repair anything.
If you have any other tips for me, I would be very grateful.
You have explored the possibilities well, at the moment I dont have more options regarding current system recovery / backup.
The encryption error resolves you by formatting the user partition by TWRP, in the option to format f2fs plus the installation of a custom Rom or Xiaomi.eu.
Look for tutorials and other reviews before testing these procedures.
Remember that there is a big achance of your ARB model as well.
Good luck.
PS. You can try dirty flash. Find an recovery Rom same version, and flash via TWRP.

[HELP] XT1794 stuck at fastboot/twrp after infinite boot anim on the latest los16

Hi everyone, I was usually providing help on this forum, now i'm the one desperate for help after some unforeseen consequences.
Bear in mind I'm kind of a noob anyway.
I have seen the message on the telegram groups for our device regarding solving the los 17 problems with the ril and camera. So i have followed the steps. I flashed the last twrp 3.4 by jarl using the official twrp app and then rebooted to recovery, wiped everything beside the internal storage and tried flashing the last los 16 zip.
And then the disaster happened. firstly the log returned error 7 so i've rebooted to recovery again and attempted to flash the same zip again without wiping anything. well the flashing worked apparently but i couldnt boot into it as it showed me an infinite boot animation.
Then i rebooted to recovery and it prompted me with a decryption key request which i didn't set before. I cancelled the prompt and I moved forward and proceeded wiping everything including the internal storage thinking that was the problem. Maybe it was maybe it wasnt, now I'm no longer prompted by any decryption key, but I was hoping i could connect to my pc through mtp, transfer some zips and flash some functional rom. Even though I enable mtp and my pc detects the phone I can't access any storage nor the internal, nor the sd card.
I tried going through multiple versions of twrp as i can still access my bootloader and i can still flash recoveries through fastboot but i feel that i'm stuck and I dont know what i should try anymore.
Before trying all this I was on an older build of los16 with the oreo firmware.
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
JarlPenguin said:
First of all, use this TWRP: https://build.twrp.me/twrp-3.4.0-0-montana.img
Second of all, do not flash TWRPSARer (if you did). Make sure the LOS16 zip isn't corrupted (which normally causes error 7), then format system, data, cache, vendor and dalvik. Reflash LOS16 and boot
Click to expand...
Click to collapse
I wasnt using the twrp sar, i was using the exact version you linked. And I can't flash any rom because i cant get the zip inside my internal memory.
You can try using adb sideload. adb sideload path/to/zip
worked like a charm. thanks a lot, Jarl.
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Some random said:
And this, is the story of someone who didn't want to wait long enough for the ROM to boot
Nah JK, but long boot-times normally = Force Encrypt Enabled
Click to expand...
Click to collapse
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Aythriel said:
it might have been the problem, but if it is it should be a disclaimer for that on the los16 page. the boot time is way longer than the usual.
Click to expand...
Click to collapse
Yes, I'll make sure to note that

Categories

Resources