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

Mate suddenly stuck in bootloop

After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?

SvenHee said:
After running Joe stones cyanogenmod10.1 for almost a year I suddenly found my phone in a bootloop
It is stuck at the boot animation, restarting it brings it back to the same state.
All I did was somehow keep one of the buttons pressed (not even sure which one), and did see the shut down/reboot menu flashing by.
The mt1 U06 does appear in my file manager (linux) but cannot be ejected, trying to connect does nothing but show progress indicator.
Tried adb reboot> device not found
fastboot recovery> waiting for device
I have started making a backup using twrp, (yes, could access it) but that may backup what's broken too...)
Any idea if this is fixable?
But also, Why, oh why did this happen?
Click to expand...
Click to collapse
Usualy for the fastboot output that you got it means you need to reinstall the drivers.
Sent from my SM-G850F

Reinstalling drivers if for windows is it not?
Until now I found that linux is super easy in installing adb and fastboot, and previously, during instalation of the phone, installing adb and fastboot was all I did.

Assuming that the 10.1 ROM still is present on your SD card try to reinstall it dirty. Just wipe cache and dalvik cache before rebooting into the system. Only the rom.

Got it working again with just a factory reset, but off course, all data and settings were gone.
I did try to put (partial) backups back but that broke the system again.
It is a shame that all my texts are gone, but I'll get over it.
Thanks for the help guys!

Nexus 5x LineageOS boot back into recovery

Hi everyone of you savior angels,
after rebooting form TWRP (3.2.1-0) following today's lineageos ota update, my phone boots: 1st/2 boot logo sequence, asks me once (out of two) for the pin code, 2/2 boot logo sequence and then after some time , 30 sec maybe, the screen blacks out and it restart into recovery mode. There, it now says "RescueParty" once I have entered the password.
I have tried to let it cool, to wipe Dalvik and Cache, and Factory Reset. Still the same. I can not find the downloaded files form the update.
I am at work now and do not have access to my usb cable.
Any thing you could recommend?
cheers

Got it!
pepite_ said:
Hi everyone of you savior angels,
after rebooting form TWRP (3.2.1-0) following today's lineageos ota update, my phone boots: 1st/2 boot logo sequence, asks me once (out of two) for the pin code, 2/2 boot logo sequence and then after some time , 30 sec maybe, the screen blacks out and it restart into recovery mode. There, it now says "RescueParty" once I have entered the password.
I have tried to let it cool, to wipe Dalvik and Cache, and Factory Reset. Still the same. I can not find the downloaded files form the update.
I am at work now and do not have access to my usb cable.
Any thing you could recommend?
cheers
Click to expand...
Click to collapse
Ok so I tried a few things.
While in recovery I could access the internal storage through my computer. First I copied all the pictures and good stuff. Then I sent to the phone a freshly downloaded latest version of LineageOS (released today). Unplugged the brick, installed the system through TWRP, rebooted. Same crap.
Thing I noticed is that if plugged on the computer or on the power adaptor, the phone would not reboot into recovery, but would stay in the second loop sequence, seemingly for ever? At least for 30 min+
Then I did the same with the previous LineageOS (last week's). Same troubles.
Right. This starts to sound like a clean wipe. So I did that. For the science, I installed the newest LineageOS version (the one that initiated the problem it seemed). Then latest openGapps. And bam! It worked!
Need to reinstall all the crap now.

Possibly Bricked?

Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED

premedicated said:
Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
Click to expand...
Click to collapse
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB. Hook up your phone to the PC and boot into the bootloader on the phone by powering on while holding in Volume Down + power. In the folder where you have fastboot on your PC, hold down shift and right click the mouse and select open command prompt (or powershell, depending on Windows version). Type fastboot devices to make sure your phone is being seen by your PC. If it is, type fastboot erase system, after that runs type fastboot erase userdata, once that runs type fastboot erase system, and finally fastboot erase boot. Then type fastboot --set-active=b , and run the same commands on that slot. Then type fastboot reboot bootloader, and when it reboots to bootloader type in flash-all.bat . That should wipe everything properly on both slots and install the latest factory image. If that doesn't work then I would say there's definitely a hardware defect. Also if it doesn't work I would try a different port on your PC.

Phalanx7621 said:
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB.
Click to expand...
Click to collapse
Inside of the factory image file, once unzipped there is another zip file contained in there with the same name. Do I need to extract that as well since it has options such as boot.img, keymaster.img and several other .img files in it, or do you just extract the main files containing bootloader-marlin-8996-012001-1808030001.img, flash-all.bat, etc.?
Phalanx7621 said:
Then type fastboot --set-active=b , and run the same commands on that slot.
Click to expand...
Click to collapse
Awesome, thanks for the reply. Question though since i'm not entirely sure about the slots. Since it's already reading it as slot B, will I change the active to slot A at some point or will running those commands in slot B erase slot A, as I understand that it basically works in whatever slot is not active.

It should detect slot A by defualt, but as long as you run those commands for both slots you'll be wiping it clean. Keep in mind we aren't talking about TWRP, we're in fastboot. And no, once you extract the files from the zip you don't need to extract the other file inside of it. The flash-all command will read it and do the proper magic. Just make sure the extracted files are in the folder with fastboot/ADB.

Well, I followed it to a T with your first post and I made it further than before. I got it all the way to where it asked if I wanted to copy files and then it froze. Restarted and it made it to finding my sim before it restarted and then it makes it to a different point before restarting, which is further than I made it before, however it still hasn't made it all the way into the software, so I guess I'm pretty well screwed unless it's something with Slot A. But I'm pretty doubtful at this point.
Update: Now it won't make it past the Google logo anymore again...

Ok, so it still isn't working. I'm going to try flashing the 8.1.0 image in a bit and see if maybe that some how resolves it. Doubtful, but it's my last step before I go spend a thousand dollars buying a new phone..
A couple questions though, when I flash-all I'm getting a lot of "Archive does not contain 'xxxxx.xxx'" errors. Archive does not contain boot.sig, boot_other.img, dtbo.img, dt.img, odm.img, product.img, product-services.img, recovery.img (this one seems important..), super.img, system.sig, vbmeta.sig and vendor.sig are all missing from the archive. This normal?
Also, I can play around in bootloader and I could in TWRP before it was erased for hours with no reboot or anything, but once the OS starts to load or loads, that's when it freezes up and fails. If it was a hardware issue shouldn't it be restarting regardless of what I'm running under?
Just trying to expend all my options before spending more ludicrous amounts of time for a piece of hardware that can just die without reason.

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?