Develop Bugs

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

Device not detected

Hello everybody,
Here my problem :
I tried to install a custom rom, I failed. Now, my smartphone stay on the Asus logo screen. I tried to follow this - http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 - to fix the problem, but when I connect phone and laptop, adb doesn't find the device.
If I continue and go in recovery mode (using TWRP), laptop can access the phone (I can see internal memory but not external).
And if I try the ADB sideload, there is no device again...
It's the first step, I don't see any other way to unbrick the phone...
Thanks in advance

http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 be lucky your phone is recognized

Hello,
Frist, thank you for your answer. I had already tried this way but nothing. Finally, I fixed the problems (detect phone and unbrick phone).
1-In TWRP, I loaded recovery.img, boot.img and droidboot.img. Reboot in recovery mod, but I had the dead droid... so I pushed on power and volume up till I have a new screen.
2-In this part, I did a Wipe/Factory reset (useless I think), reboot in recovery mode (still dead droid). This time I selected the line "update with adb" (with an ASUS firmware). Then I had a message who told me update adb sideload. I did it and it installed the firmware. The smartphone reboot correctly.
Now, I have the same problem I had yesterday. In TWRP, my external storage isn't detected...

you use stock recovery or custom recovery, if you use stock recovery external-storage won't detected

Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Edit : I guess custom, TWRP. It's why I don't understand why it doesn't allow me to mount SD card or doesn't detect this same SD Card.

Mara Udé said:
Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Click to expand...
Click to collapse
i use twrp 3.0 too, but external sd detected. no need to put on external storage, you can flash Cm 13 through internal storage
if you want to install custom rom it's better if you make a backup first, so if happen you failed when installing new rom or maybe you don't like it (new rom) you can go back to stock rom through TWRP restore

Ok, failed again...

Try a different rom or redownload the rom it might have been a bad download.
The error message says there is no updater script in the zip meaning it can't install anything as the updater script tells what directories to install the files if I seen it correctly that is.
Sent from my ASUS_Z00AD using Tapatalk

Mara Udé said:
Ok, failed again...
Click to expand...
Click to collapse
maybe the CM 13 zip file you have download corrupted, try to re-download and re-flash it again. if still failed try another rom
( i'm using AICP Rom "based on CM 13 too") try it, it's awesome Rom ---> do clean install wipe all except internal storage and external storage
http://forum.xda-developers.com/zenfone2/development/rom-c-p-t3285951/post64645756#post64645756
http://opengapps.org/ ( select x86-6.0-nano )

Hi,
Sorry for this late answer. As I failed to install those roms (CM13, Bliss), I'm going to stop here and wait for the Marsmallow update. But I'm happy my phone isn't brik anymore.
Thank you all.

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.

A bit frustrated but looking for help - TWRP shows all memory as 0mb

Hi guys,
I followed LineageOS for a while and bit the bullet to try it on my Xaomi Mi A1. After learning everything about the bootloader and getting the files I needed ready, I formatted my device to find that I can't load up the .zip from TWRP.
My microSD shows as 0mb (as does all the internal memory) and I can't access any /data folder a lot of people talk about (it's just not there). I can't mount the microSD from TWRP since it just won't let me select, and I tried to refollow all the steps a few times.
I'm pretty worn out and beat (it's literally everything I've been doing in my free time) so I would really appreciate any extra help. I'll keep an eye on this thread, so do let me know if I can provide any additional information.
Quick facts:
- TWRP boots up fine
- Non rooted Xaomi Mi A1
- Latest Android update
- I run Linux at home but have access to Wine/Windows if needed
- microSD otherwise works on computer and phone just fine
edit: Added a poll cus I'm bored. You can probably tell what country I'm from based on it. I'll keep updating as I figure this misery out

Update: I'm trying the unofficial 3.2.3 TWRP as seen on the Xaomi board here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
Will post updates.
Update: Didn't work. I've tried every TWRP I can find online for Xiaomi as well as everything on the Xiaomi subsection of this forum. I read something about how if you try to flash with fastboot you need to flash it with the official stock boot.img, so I'm downloading that from http://en.miui.com/download-333.html and will try to flash that when I have time tomorrow.

Can't boot up phone at all anymore. Gets stuck at Android screen. Running TWRP and trying to Factory Reset gives Failed to mount '/data'.
edit: Can't mount anything
edit: The link above saved my phone just before I needed it for work. Nice. Trying again tomorrow!

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.