Encryption fails?? - Oppo Find 7 and 7a

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.

Related

Device bricked? No adb-access

Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco
Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there
Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!
That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.

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.

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.

[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