Hello, it's 2nd day and I don't have phone.
Tried to encrypt with lollipop, it failed and now what ever I do it starts with the "encryption failed" screen.
I formated everything, reflashed, restorer from backup, tried both twrp and cwm recoveries
nothing worked.
anyone has any solutions?
pika456 said:
Hello, it's 2nd day and I don't have phone.
Tried to encrypt with lollipop, it failed and now what ever I do it starts with the "encryption failed" screen.
I formated everything, reflashed, restorer from backup, tried both twrp and cwm recoveries
nothing worked.
anyone has any solutions?
Click to expand...
Click to collapse
Maybe this post can help you:
http://forum.xda-developers.com/showpost.php?p=52773721&postcount=2
Make sure to select format. That's something different then wipe.
Thanks for the reply, but nothing worked.
Finally the only solution was to go stock.
Downloaded the stock lollipop for odin, flashed partitioned etc and rebooted
Of course the "encryption failed" error came up again,
but this time the stock recovery managed to wipe the encryption.
from there I start from scratch, new recovery, new root, new setup
and then restore from backup.
My new job has high risk of "loosing" my phone so I could really use the encryption, for all my sensitive data.
apparently it is not working.
The problem is the custom rom? the custom kernel? the custom recovery?
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.
Hi. I am currently running the latest lineage is. I recently tried the aosp pie build and also the unofficial lineage 16. I ran into some trouble restoring my phone back to lineage when I was done trying out pie. My twrp backups are not restoring for some reason. I am on the latest version of twrp. I also encrypted my data partion so now I have to put my password on before I boot into recovery and before my phone boots up. I also had a hard time getting it to read my sim card after I installed lineage fresh.
So first thing does anyone have any idea why my backups are not restoring or how to fix the issue?
And the second thing is i want to get rid of the encryption. So how do I do that. Do I wipe all my partions and then push fresh copies of lineage and gapps to my phone from my PC?
mojorisin7178 said:
Hi. I am currently running the latest lineage is. I recently tried the aosp pie build and also the unofficial lineage 16. I ran into some trouble restoring my phone back to lineage when I was done trying out pie. My twrp backups are not restoring for some reason. I am on the latest version of twrp. I also encrypted my data partion so now I have to put my password on before I boot into recovery and before my phone boots up. I also had a hard time getting it to read my sim card after I installed lineage fresh.
So first thing does anyone have any idea why my backups are not restoring or how to fix the issue?
And the second thing is i want to get rid of the encryption. So how do I do that. Do I wipe all my partions and then push fresh copies of lineage and gapps to my phone from my PC?
Click to expand...
Click to collapse
The errors you get when trying to restore your TWRP backups would help a lot with answering why they fail
Your right I should know better. I didn't write them down. It's been a while for me. Anyway I got my phone working really good now. I have to make a backup of my current system. After I do that I will try to restore the old one and see if it gives me the error msg and post it. If not then next time I run into a problem I will make sure I pay attention to the details so I can give a s much info as possible.
I bought a new XT1575 a couple of weeks ago. Once I'd read enough to have confidence I followed the instructions to extract that long number to paste into the form on the Motorola web site and ask them to send me a code. They did, I input the code, I got a notice that my bootloader was unlocked. Once that was done I installed TWRP via ABD (I think, whatever the directions said). TWRP worked, I wiped the stock OS, flashed a custom ROM (Lineage 14) and everything worked perfectly.
Today I wanted to backup my existing ROM, wipe the device and install a different custom ROM. I booted into TWRP and I think it completed the backup. When I went to wipe though, it would crash partway through and boot back to the bootloader unlocked screen. If I tried to simply overwrite the existing ROM with the new ROM that would crash and boot to the bootloader unlocked screen too. Now I can't complete a backup either.
As I'm writing this I'm wondering if the micro USB card could be at fault, since that's where I want to back up to and that's where the new ROM is. However, if it was a corrupted card wouldn't the wipe function still work?
Any idea if reflashing TWRP would solve my problem? Any better solutions?
Hi,
Am just a newbie in flashing roms and stuff like that. I have a note 2 GT-N7100 that was running 4.4.2. KitKat. I decicided to root the device and it was successful. Flash TWRP all went well. Then I tried flashing a custom ROM. I read about backups so I made a backup before flashing the ROM ViperOS 7.1.2. Flash Gapps and it was successful. But my Sim was not detected. So I retored backup and was back in 4.4.2. and the sim was detected. Unfortunately for me, my backup was in the internal memory of the phone. I thought the ViperOS was just faulty somehow not to have read my sim. So I tried a Marchmellow custom ROM from a site I can't remember. The phone got stock at Samsung Logo. I waited long time to no avail. Instead of clearing cache n dalvic I included internal memory and data. That was how I lost the back up. It took me to the stock recovery. I wipe data / factory reset. Still got stock at boot loop. I flashed TWRP via odin and it was successful. I flashed the viperOS it works but no Sim. I read through some threads and understood I lost my IMEI. I checked it was unknown. Baseband unknown. Tried a couple of proposed measures but to no avail. I thought the best thing was to go back to stock.
When I flash the stock, with odin it fail. I don't want to believe it can be cable or port issues since I flash TWRP successful. I tried flashfire. The flash completes bit it says "failed to mount cache. Invalid argument. Read that I have to mount and clear cache. Did all that with no success. For 5 days now. I really need help. Don't know what to do. Pls help me.
Thanks.
Am sorry for writing too much