Database Info

[Q] Twrp With Encrypted Oneplus and Lollipop

I have installed the CyanogenMod 12 nightlys on my OnePlus using TWRP.
After setting my phone up how I wanted it, I encrypted my phone, not thinking it would cause any issues.
I now want to update to the latest nightly but TWRP will not install anything as it cannot mount any of the volumes.
I assume this is because I encrypted it.
There doesn't seem to be a way to decrypt my phone and there's no way to get to anything in TWRP.
So far I've tried reflashing my bootloader but still can't mount the volumes I need to wipe to reinstall the ROM.
How do I wipe them with the volume being encrypted? Where do I go from here? Thanks in advance!

TWRP / Lollipop encryption bug
See Bug #333 on TWRP's github.com site

Cyanogenmod update fails with error 7

Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.

Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351

Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom

The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September

Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.

I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off

You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)

Thanks, i will try it and report

The last build i found for my version is 1.27. this is what i have

Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.

Is there a solution without going back to stock?

I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...

thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....

I'm glad to hear it worked for you!

Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.

That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.

Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255

I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.

Any news to this theme? Is Twrp able to handle A9 again in new Version?

The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.

What did TWRP do to my tablet?

I installed TWRP. It was supposed to be TWRP 2.8.6.0, but it is 2.8.5.0. Today, I just backed up my tablet with it. After using TWRP, my tablet boots up 6 times faster and the UI functions twice as fast as it did before. Overall, my tablet got better after running TWRP. So, what did it do? Also, I want to flash Lollipop. Can I do that with this version?

I don't know what twrp did to your tablet. If you want to flash a lollipop or a marshmallow rom however you should use this version of twrp : http://forum.xda-developers.com/gal...overy-team-win-recovery-project-twrp-t3464050
And use one of theses rom :
lollipop : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-12-cm12-t2997934
Marshmallow (recommended) : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798

Ka-B00M said:
I installed TWRP. It was supposed to be TWRP 2.8.6.0, but it is 2.8.5.0. Today, I just backed up my tablet with it. After using TWRP, my tablet boots up 6 times faster and the UI functions twice as fast as it did before. Overall, my tablet got better after running TWRP. So, what did it do? Also, I want to flash Lollipop. Can I do that with this version?
Click to expand...
Click to collapse
twrp manage all general functions before the android system completely started. you can compare twrp with the bios system on your pc.
if you want install the latest roms, you should upgrade your twrp to the latest unofficial common version (3.0.2-6). you can find it here: http://andi34.github.io/recoveries_tab2.html

smart-t78 said:
twrp manage all general functions before the android system completely started. you can compare twrp with the bios system on your pc.
if you want install the latest roms, you should upgrade your twrp to the latest unofficial common version (3.0.2-6). you can find it here: http://andi34.github.io/recoveries_tab2.html
Click to expand...
Click to collapse
Can I flash the linked recovery using the recovery I already have? If not, how can i do it? I do not have a PC, BTW.

Ka-B00M said:
Can I flash the linked recovery using the recovery I already have? If not, how can i do it? I do not have a PC, BTW.
Click to expand...
Click to collapse
yes, you can install the new version with your current twrp.

smart-t78 said:
yes, you can install the new version with your current twrp.
Click to expand...
Click to collapse
Awesome.
It's official, my device will be upgraded. May the force be with us all!

XT926 from 4.1.1 to LineageOS 14.1

I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted

retalger said:
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
Click to expand...
Click to collapse
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.

SOLVED
OGdroidster said:
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
Click to expand...
Click to collapse
Oh! Thank you so much for the help.

retalger said:
Oh! Thank you so much for the help.
Click to expand...
Click to collapse
Sure your welcome

Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.

drkdeath5000 said:
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
Click to expand...
Click to collapse
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.

thunder2132 said:
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
Click to expand...
Click to collapse
I tried this last weekend but was getting constant force closes from System UI so i gave up and went back to the MokeeOS build.

Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.

polyzen said:
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
Click to expand...
Click to collapse
Nice! I'm glad you got it working.

what do you mean with reflashed factory image 4.1.2?

I was on Resurrection Remix for the Razr M and now flashed LOS from this thread because of connectivity problems and I hoped it is a problem of RR. But unfortunately I still just have Edge connection, no 3G or 4G. Does anyone know how to fix that? There were no problems under 4.1.
Edit: I went back to 4.1.2 and wanted to start from zero but now on 4.1.2 there's only Edge connection as well :/

failed attempt to downgrade OS - will reflashing the latest version fix this issue?

So I did a stupid move by flashing a lower-version (OOS 9.0.3) over the latest version in hopes it would downgrade.
Of course, this failed, and now I'm always bootlooping to my recovery (TWRP), but it never asks for an encryption password anymore (meaning I can't access my files).
Would flashing the latest version of OOS fix this issue? And if so, how am I supposed to flash it?

alrightthen said:
So I did a stupid move by flashing a lower-version (OOS 9.0.3) over the latest version in hopes it would downgrade.
Of course, this failed, and now I'm always bootlooping to my recovery (TWRP), but it never asks for an encryption password anymore (meaning I can't access my files).
Would flashing the latest version of OOS fix this issue? And if so, how am I supposed to flash it?
Click to expand...
Click to collapse
Use the unbrick tool in the guide section.

alrightthen said:
So I did a stupid move by flashing a lower-version (OOS 9.0.3) over the latest version in hopes it would downgrade.
Of course, this failed, and now I'm always bootlooping to my recovery (TWRP), but it never asks for an encryption password anymore (meaning I can't access my files).
Would flashing the latest version of OOS fix this issue? And if so, how am I supposed to flash it?
Click to expand...
Click to collapse
You have 2 choices. First to fix this now and stay on this version, in twrp, just format data and phone will boot. Second, you could just flash the latest version in fastboot mode to save your data. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 here is link to the fastboot rom thread.