well i updated my nexus 9 through OTA update to android 6.0 couple days ago, then i had some battery issue.
So then i tried to flash cm12.1
what i did was, i unlock my device flash TWRP 2.8.7.0, then i got this corrupted message upon rebooting my device.
i did some research(i should've done it before doing anything:silly, it seems like it's something about the force encryption?
i tried almost every guide on xda here, flash de-crypted boot, flash stock recover, flash stock rom, adb sideload function is not working, nothing seems to work?
it seems like nothing can write onto my device as long as it's encrypted?
it works fine now, just wondering if there's a way i can properly de-crypt my device in this state and go back to 5.1.1 or CM12.1
Thanks
TWRP has just been update to 2871 and can now read encrypted partitions. Install this new TWRP.
Sent from my Nexus 9
Related
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
you should write this in other section but i want to help you.
maybe try to flash stock kdz again if you still can then check if bootloader method you use is correct but if was not you will brick your phone.
Hello!
This is my first post. I've searched for hours. Visited over 200 sites and forums tried multiple things installed all available android tools you can find online and i am seriously stuck.
Setup before problem : One Plus X - Cm13 - Version 2016 - Oct - 10. This is updated from the cyanogen website and its treated as the stable version.
Downloaded the latest version which is the 15th and got stuck at bootloop. After some searching i discovered that i had to updated my bootloader as it was the same since November 2015. In the website that i got the new version i was also given the new TWRP version 3.0.2 . So i went into my recovery flashed the new bootloader , then the TWRP , then the new ROM. Mobile boots up shows completly empty fresh install CM 13 without gapps or any of my previously installed programs. Everything is still in the storage. All installation folders from the various programms i had.
My recovery mode refuses to Boot. It just stays on the one plus logo. Tried TWRP manager from the OS but the old version 2.8.7.0 refuses to be unistalled. Adb command lines : I've been trying on windows 10 , 8 , 7 with the appropriate drivers and the only thing that i can make the phone do is go to either FASTBOOT or normal boot. Flashed the TWRP multiple times and no changes what so ever. I can make the mobile show up with ADB device, Fastboot device it shows success and when i try to boot into recovery it just gets stuck. I also got the MTP package from Windows. Basically i bricked my phone within a glass. OS works but Recovery not. Fastboot is supposignly working but i see no changes.
Thank you in advance!
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Exodusche said:
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Click to expand...
Click to collapse
Thank you i managed yesterday from a program to flash twrp as kernel and was rebooted into a working twrp and fixed everything from there.
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
Hi friends,
So here's a thing:
I was trying to update my Nexus 9 to the latest Slimrom build , and I used Chainfire's flashfire app. It didn't work and sent the tablet in a boot loop. But it also wiped my recovery so I couldn't even select my recovery.
So no issues, I used the Wugfresh nexus toolkit to flash it back to stock and unroot. Bootloader is still unlocked, so I just root it again and go ahead and try to install the update using Wugfresh. It works, but says the vendor.img is wrong. So I downloaded the correct vendor.img and tried to flash it, but of course because the tablet is encrypted TWRP asked for a password. I hit cancel and tried to continue, but Wugfresh just hung at that step.
So I tried to manually flash the ROM, but now it gives me a vendor.img error and will not flash anything. Trying to flash anything sends the device in a bootloop.
TLDR; I can restore to stock and root, and also access the bootloader and recovery (TWRP) but can't flash anything without sending the device in a bootloop.
I've currently restored the tablet to stock via wugfresh's tool and rooted. So I'm back at the beginning, except with this vendor.img issue when I'm trying to flash a ROM.
Anyone have any ideas?
Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.