Hi!
Since last year I used CM14.1 and now decided to upgrade to LOS14.1.
After installing LOS14.1 via TWRP (after wiping data-cache-system) I tried to encrypt the phone, but after rebooting, it came up unencrypted.
Tried another round with clean installs of LOS14.1 and XenonHD7.1, both didn't work.
I already went back to OP original recovery and OxygenOS 3.5.8, even there the phone claims to encrypt, reboots and comes back after a few seconds unencrypted.
Any idea, what to change to get the OP2 encrypted?
Regards,
Hemingway
Take a backup by connecting your phone in twrp to pc. It should show as a mass storage.
Then you need to go to wipe > format data.
This will completely wipe your data. Then copy your rom back to your phone in twrp and flash.
This should fix it.
Hi everyone,
I have been happy with the Marshmellow version the OS since I bought my phone when it came out (Unlocked, Encrypted). I have performed one update since I had the phone. Today, after seeing the latest posts after not being on this site for a year, I decided to make the move to upgrade to OOS 5.1.0!! Why not, nothing else going on this weekend. I upgrade TWRP to 3.2.1-1, I make a full backup, I follow the upgrade instructions... it fails with the continuous spinning balls on reboot. I Do some research... oh, it is "challenging" to upgrade but possible. No big deal, I will just restore my backup and try again at some other time. My backup restore fails Error 255, I try the fixeS I found such as unmounting data... No Luck). Can not restore the data partition. I guess I should have decrypted everything prior to backing up based on what I read later.
I at least backed up my SD card using adb prior to all this, so I decided to just reinstall ANY OS to get my phone running again for tonight. Well I have not had much luck. I downgraded TWRP to 3.2.1-0, I have tried installing:
OnePlus5Oxygen_23_OTA_033_all_1804110400_eb1766 - Originally installed with not errors but phone reboots back into TWRP after a failed 1st reboot. (I do get a "failed to mount /vendor")
lineage-15.1-20180423-nightly-cheeseburger-signed with Gapps (Gapps failed with I think a error 7)
I was messing with the data partition, wiped, formatted, etc. I am sure this is some of the issues. One other thing is that TWRP always boots to the "keep System Read only" I find this strange and had never seen before. I select to allow modification, but it seems like nothing changes on reboot.
At this point I would just like to get a stock OS image on the phone. IS there something I am missing?
https://forum.xda-developers.com/oneplus-5/how-to/guide-mega-unbrick-guide-hard-bricked-t3698370
Sounds good, let me give it a try.
I've been thru this already. Here is the simplest way to get your 1+5 back to work, while having the latest LineageOS installed. It takes a bit of time and patience, but it works:
Using fastboot, reinstall TWRP 3.2.1-1 (or newer, if any)
Wipe all partitions, namely Dalvik/ART cache, Cache, System, Data and Internal storage
Sideload the latest OOS (version 5.10 or later, if any) with Android 8.1. This version will be OK for LineageOS 15.1 and you will no longer have that stupid error 7 when installing LOS 15.1
If OOS boots into recovery and asks for passwords or PIN or schema ... click on the "forgotten" link. OOS Recovery will then remove encryption and wipe out any data that was left.
Reboot phone, and start OOS session. Do not use any security stuff (PIN or schema or whatever) that would encrypt the phone. At least not now - If necessary, you will add it at the end of this whole process.
Once OOS is working, reboot to Bootloader. Since TWRP has been erased with OOS default recovery, you will have to reinstall it.
From TWRP, wipe Dalvik/ART cache, Cache, and Data partitions. This time, do not touch System or Internal storage
Sideload Lineage OS latest version. If you need to use Google Apps (e.g. Open Gapps), sideload it now before rebooting
Reboot (you might have to reboot twice, don't worry about that).
Once booted in LineageOS, do whatever you like - add accounts, root phone, etc.
Enjoy! (you may want to shout "Vive la France!", well ... don't hesitate!)
Sorry for my poor English. If anything here is unclear to you, please let me know.
I Have no idea what happened. I came home to start working on my phone, powered it up, and boom I have Android 8.1. Ok, Whatever...
Now I wonder if I should go for lineage or not.
kuhnto said:
Now I wonder if I should go for lineage or not.
Click to expand...
Click to collapse
It all depends on how important privacy is to you. If you don't care, then stick to the original OnePlus firmware. If you do, then switch to LineageOS.
I had AOSPEX room on my sm-g530w 8.1 Oreo with restored efs, modem and firmware from stock backup, but after not enjoying the experience I tried to switch to Resurrection Remix 7.1.2 nougat, also with restored efs, firmware and modem.
On the first boot I realized it was a boot loop as it kept on vibrating after certain intervals of time. I decided to switch back to stock rom and restore a backup I made, but it kept giving me error 255. I gave up and reflashed AOSPEX room without restoring efs and other partitions. None of the reboot options worked as no matter where I wanted to boot (power off, download mode), it brought me back to twrp. I then tried to force reboot my device and at a first glance it seems to work. Should I restore the partitions again, and how screwed is my device?
Hey,
I didn't updated my phone for quite some time and today I had some free time and I decided to update it to the latest version. I performed the first OTA update, and the process wen't really smooth. The phone booted after a few minutes, however it told me there's another system updated so I installed it as well.
However, after installing the second OTA update, my phone never booted again. it stucks in bootloop for a few minutes and then just boots to recovery.
I don't really know what to do, and although most of my data is backed up I really want to avoid wiping all the data.
The phone was never rooted and has stock recovery. How can I make it boot without wiping all the data? I did try to wipe cache already and it didn't help.
I see that there is a method called 'adb sideload' but I want to be sure it doesn't wipe data and to know which zip I should give it... Thanks!
I have an Axon 7. It was previously running TWRP 3.2.3.0L v1.3 and crDroid 9.0-20200514. The device had full disk encryption enabled.
I couldn't get Google Play Services to work using any of the standard tricks. I decided to factory reset via Settings.
My device rebooted into TWRP, which asked for my device password. When I entered it, it didn't accept it. (I had earlier run into this problem when I considered trying to update my ROM. I decided against it, because I couldn't get TWRP to mount my data partition.).
I figured while I was in TWRP anyway, and since I had already committed to factory reset, I would just prepare to flash the updated ROM.
Following the crDroid instructions here, I wiped cache, system, vendor, and data from within TWRP.
Unfortunately, I then accidentally rebooted before I flashed the new ROM.
My phone is now stuck at the boot screen. I cannot get into recovery. I can, however, get into EDL. (Edited to add: the device also shows up in Windows 10 Device Manager as Qualcom HS-USB 9008, so I should be able to use the Axon7_EDL_Tool.)
The good news is that I have everything backed up (using Titanium, and I have a several month old nandroid backup). Is there any way I can make this device work again?
I would suggest the following:
- Use Axon7_EDL_Tool to flash a full ROM
- Use Axon7_EDL_Tool to flash TWRP
- Use TWRP to flash crDroid
- restore your settings and apps with Titanium Backup