[ROM][A5000 | cheeseburger][8.1.X][OFFICIAL] LineageOS 15.1 (Oreo) for Oneplus 5

[SchroedingersCat]

Flash 5.1.7 firmware and then try upgrading to a newer build.

How can I do that with TWRP not being able to decrypt my partitions? Is downgrading TWRP the only option?

---------- Post added at 12:45 PM ---------- Previous post was at 12:11 PM ----------

Flash 5.1.7 firmware and then try upgrading to a newer build.

Reading helps: https://download.lineageos.org/cheeseburger/changes/

I'm sorry! I completely forgot that my phone is already on 5.1.7 firmware. I should have thought about that before posting.

Because TWRP was unable to read anything from my encrypted phone on TWRP v3.2.2 and v3.2.3, I downgraded TWRP to v3.2.1-1. So reading encrypted phones with these versions is broken. The bug tracker of TWRP has a lot of issue related to that, so it seems best to avoid these versions at all (https://github.com/TeamWin/Team-Win-Recovery-Project/issues?utf8=✓&q=decrypt).

Just to be sure, I reflashed OOS stable 5.1.7 firmware (https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8). But upgrading to LineageOS build from Dec. 1st still fails. This time, I found a way in TWRP to show the log:

Checking for MODEM build time-stamp 2018-11-06 18:11:36
Error: This package requires firmware version 5.1.7 or newer. Please upgrade firmware and retry!
Updater process ended with ERROR: 7

But I already flashed 5.1.7.
Why does TWRP fail to recognize my correct firmware version?

 

[mp3deviant721]

How can I do that with TWRP not being able to decrypt my partitions? Is downgrading TWRP the only option?

---------- Post added at 12:45 PM ---------- Previous post was at 12:11 PM ----------



I'm sorry! I completely forgot that my phone is already on 5.1.7 firmware. I should have thought about that before posting.

Because TWRP was unable to read anything from my encrypted phone on TWRP v3.2.2 and v3.2.3, I downgraded TWRP to v3.2.1-1. So reading encrypted phones with these versions is broken. The bug tracker of TWRP has a lot of issue related to that, so it seems best to avoid these versions at all (https://github.com/TeamWin/Team-Win-Recovery-Project/issues?utf8=✓&q=decrypt).

Just to be sure, I reflashed OOS stable 5.1.7 firmware (https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8). But upgrading to LineageOS build from Dec. 1st still fails. This time, I found a way in TWRP to show the log:

But I already flashed 5.1.7.
Why does TWRP fail to recognize my correct firmware version?

Hey. I'm just throwing ideas out but did you try to redownload the ROM or try a different dated zip? Or even a different ROM?

 

[SchroedingersCat]

Hey. I'm just throwing ideas out but did you try to redownload the ROM or try a different dated zip? Or even a different ROM?

I just downloaded the build from Nov. 21st, but flashing the update gives me the same error.

Why would flashing a different ROM (like Oxygen OS?) by of help? Would I lose all my installed apps?

 

[mp3deviant721]

I just downloaded the build from Nov. 21st, but flashing the update gives me the same error.

Nov 21st build was before the 5.1.7 blob update though iirc. But it seems like it might be an issue with recovery or your set up. Try Blu Spark recovery if you have not tried that.

Why would flashing a different ROM (like Oxygen OS?) by of help? Would I lose all my installed apps?

It's just to narrow down if its the zip or recovery/device set up.

 

[Portgas D. Ace]

How can I do that with TWRP not being able to decrypt my partitions? Is downgrading TWRP the only option?

---------- Post added at 12:45 PM ---------- Previous post was at 12:11 PM ----------



I'm sorry! I completely forgot that my phone is already on 5.1.7 firmware. I should have thought about that before posting.

Because TWRP was unable to read anything from my encrypted phone on TWRP v3.2.2 and v3.2.3, I downgraded TWRP to v3.2.1-1. So reading encrypted phones with these versions is broken. The bug tracker of TWRP has a lot of issue related to that, so it seems best to avoid these versions at all (https://github.com/TeamWin/Team-Win-Recovery-Project/issues?utf8=✓&q=decrypt).

Just to be sure, I reflashed OOS stable 5.1.7 firmware (https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8). But upgrading to LineageOS build from Dec. 1st still fails. This time, I found a way in TWRP to show the log:

But I already flashed 5.1.7.
Why does TWRP fail to recognize my correct firmware version?

Please ensure that you are using the latest TWRP by codeworkx. The latest version doesn't have issues with encryption.

 

[SchroedingersCat]

Nov 21st build was before the 5.1.7 blob update though iirc. But it seems like it might be an issue with recovery or your set up. Try Blu Spark recovery if you have not tried that.

I just checked https://download.lineageos.org/cheeseburger/changes/ and 5.1.7 was added exactly on Nov. 21st.

I'll try Blu Spark. Is it that one https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933 ?

It's just to narrow down if its the zip or recovery/device set up.

Would I lose all my installed apps if I flashed another ROM like OOS?

---------- Post added at 02:29 PM ---------- Previous post was at 02:19 PM ----------

Please ensure that you are using the latest TWRP by codeworkx. The latest version doesn't have issues with encryption.

As I have written earlier, the latest version of TWRP is 3.2.3.0, according to this site https://eu.dl.twrp.me/cheeseburger/ . Once I flashed that version 3.2.3 (either official or codeworkx from https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723) or v3.2.2, TWRP stops asking for an encryption password and is unable to mount any partition. Either it just doesn't mount the partition or the mounted partition is empty or the mounted partition shows encrypted garbage files and folders, depending on the version of TWRP. Once I'm back on TWRP v3.2.1-1, the encryption issue is gone. Also have a look at TWRP's bug tracker, there a multiple recent issues with decryption.

I guess from what you are writing that you used to have issues with encryption on some versions of TWRP. Which versions were the ones that broke encryption for you?

 

[mp3deviant721]

I just checked https://download.lineageos.org/cheeseburger/changes/ and it was added exactly on Nov. 21st.

I use a different website to check commits and it shows 11/25 when 5.1.7 was added. Lineage's own website is probably more correct... But you have proven that it isn't an issue with the zips. So it doesn't really matter right now.

I'll try Blu Spark. Is it that one https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933 ?

That's the one. That recovery usually works pretty good.

Would I lose all my installed apps if I flashed another ROM like OOS?

Yes. You do want to clean flash when changing ROMs (either from custom to custom or custom to OOS and vice versa).

 

[Portgas D. Ace]

I just checked https://download.lineageos.org/cheeseburger/changes/ and 5.1.7 was added exactly on Nov. 21st.

I'll try Blu Spark. Is it that one https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933 ?


Would I lose all my installed apps if I flashed another ROM like OOS?

---------- Post added at 02:29 PM ---------- Previous post was at 02:19 PM ----------



As I have written earlier, the latest version of TWRP is 3.2.3.0, according to this site https://eu.dl.twrp.me/cheeseburger/ . Once I flashed that version 3.2.3 (either official or codeworkx from https://forum.xda-developers.com/on...very-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723) or v3.2.2, TWRP stops asking for an encryption password and is unable to mount any partition. Either it just doesn't mount the partition or the mounted partition is empty or the mounted partition shows encrypted garbage files and folders, depending on the version of TWRP. Once I'm back on TWRP v3.2.1-1, the encryption issue is gone. Also have a look at TWRP's bug tracker, there a multiple recent issues with decryption.

I guess from what you are writing that you used to have issues with encryption on some versions of TWRP. Which versions were the ones that broke encryption for you?

I dont have had any encrytion issues, but others had. The latest version by codeworkx solves those issues (at least I didn't see any complaints about it since its release).

 

[SchroedingersCat]

That's the one. That recovery usually works pretty good.

I tried both blue spark versions (custom and non-custom) but both won't boot into recovery mode. Instead, the OP5 boots into fast mode. Again, everything works fine as soon as I flash TWRP 3.2.1-1 (except for flashing the updates).

---------- Post added at 11:40 PM ---------- Previous post was at 11:38 PM ----------

I dont have had any encrytion issues, but others had. The latest version by codeworkx solves those issues (at least I didn't see any complaints about it since its release).

So that makes it even more likely that this is a regression. Fixing an issue just some people had does not mean you don't introduce a new problem. To me, the problems start as soon as I flash TWRP v3.2.2, so whatever the issue is, it has been added there.

 

[Coumodo]

All December releases gave me a lock screen issue.
Pressing power button unlocks device and show my home screen, but I can't do anything. Device doesn't reaction to any input.
I have to press power button twice to lock and unlock again. Than I can insert my pin or unlock device by fingerprint reader. Its annoying to wakeup device always twice for using...
Seems its related to smart lock feature.

Gesendet von meinem ONEPLUS A5000 mit Tapatalk

 

[nonplayercharacter]

I'm having the same issues as Schroedinger's Cat

Oneplus5
1. Flashed OOS 5.1.7 for cheeseburger full zip (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)

2. Fastboot flash recovery CodeWorkX TWRP 3.2.3 (https://forum.xda-developers.com/oneplus-5/development/recovery-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 ; https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/) -this did fix the problem of seeing no files in /SDCARD

3. TWRP -> Format Data, then Wipe dalvik and cache, then Reboot to Recovery so the SDCARD is visible and can have files written to it.

4. ADB push LineageOS 15.1 latest official nightly zip to /SDCARD/ (https://download.lineageos.org/cheeseburger ; https://mirrorbits.lineageos.org/fu...15.1-20181210-nightly-cheeseburger-signed.zip )

EDIT!: ADB push CodeWorkx cheeseburger 5.1.7 firmware (https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/firmware/)


5. TWRP -> Install CodeWorkx 5.1.7 firmware


6. TWRP -> Install LineageOS offical 15.1 zip


7. Get same error as reported by SchroedingersCat about requiring 5.1.7 firmware

7. FIXED by flashing CodeWorkx 5.1.7 firmware before LineageOS zip. Thank you!

 

[codeworkx]

I'm having the same issues as Schroedinger's Cat

Oneplus5
1. Flashed OOS 5.1.7 for cheeseburger full zip (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)

2. Fastboot flash recovery CodeWorkX TWRP 3.2.3 (https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 ; https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/) -this did fix the problem of seeing no files in /SDCARD

3. TWRP -> Format Data, then Wipe dalvik and cache

4. ADB push LineageOS 15.1 latest official nightly zip to /SDCARD/ (https://download.lineageos.org/cheeseburger ; https://mirrorbits.lineageos.org/fu...15.1-20181210-nightly-cheeseburger-signed.zip )

5. TWRP -> Install LineageOS 15.1 zip

6. Get same error as reported by SchroedingersCat about requiring 5.1.7 firmware

Try to flash the firmware file provided by us. See op.

Sent from my OnePlus 6 using XDA Labs

 

[nonplayercharacter]

Try to flash the firmware file provided by us. See op.

Sent from my OnePlus 6 using XDA Labs

That fixed the issue. Thank you CodeWorkX! LineageOS 15.1 working great.

 

[SchroedingersCat]

I didn't know that we have to use the modified 5.1.7 firmware. Thanks for mentioning it.

@codeworkx aren't users supposed to flash the original firmwares rather than the modified ones?

At SourceForge (found at downloads link above) we also occasionally provide firmware zips or custom built TWRPs.

We use them when developing and also make them available to others, but please note they are unsupported.
They are good enough for us developing but might not be good enough for everyone's usecases.

 

[ym1cky]

I dont know how to make a logcat during reboot for Bug report so maybe somebody can do this.
The silent profile is on loud after reboot while slider is on top position for silent. I have to slide down and up again.

 

[codeworkx]

I didn't know that we have to use the modified 5.1.7 firmware. Thanks for mentioning it.

@codeworkx aren't users supposed to flash the original firmwares rather than the modified ones?

Those files are extracted from the official releases downloaded from oneplus website.

Looks like the zip of the 5.1.7 full rom he downloaded is somehow corrupt. So better use ours.

Sent from my OnePlus 6 using XDA Labs

 

[nonplayercharacter]

Those files are extracted from the official releases downloaded from oneplus website.

Looks like the zip of the 5.1.7 full rom he downloaded is somehow corrupt. So better use ours.

Sent from my OnePlus 6 using XDA Labs

Could the problem have been caused because I flashed the full OOS zip, but then TWRP -> Format data and wipe Dalvik + Cache? Does the full OOS zip's firmware survive after the format and wipe?

 

[d1n0x]

Could the problem have been caused because I flashed the full OOS zip, but then TWRP -> Format data and wipe Dalvik + Cache? Does the full OOS zip's firmware survive after the format and wipe?

Yes it does, or you wouldn't have a working phone after flashing a ROM.

 

[nonplayercharacter]

Yes it does, or you wouldn't have a working phone after flashing a ROM.

Interesting, so when TWRP flashes a ROM it goes to Data, but when TWRP flashes the custom 5.1.7 firmware it gets stored somewhere else? (Somewhere that doesn't get formatted in Factory Reset) Where does it get stored? Do you know of any good documentation where I could learn about these?

BTW I was inspired to try CodeWorkX LineageOS 16.0, with the necessary 16.0 custom TWRP and custom firmware. It seems to work flawlessly so I moved to 16.0.

 

[codeworkx]

Interesting, so when TWRP flashes a ROM it goes to Data, but when TWRP flashes the custom 5.1.7 firmware it gets stored somewhere else? (Somewhere that doesn't get formatted in Factory Reset) Where does it get stored? Do you know of any good documentation where I could learn about these?

BTW I was inspired to try CodeWorkX LineageOS 16.0, with the necessary 16.0 custom TWRP and custom firmware. It seems to work flawlessly so I moved to 16.0.

The internal storage is split into like 20 partitions.

primary bootloader, secondary bootloader, dsp, persist, modem, boot, recovery, system, vendor, data, cache .....

Only data and cache are getting "reset".


Sent from my OnePlus 6 using XDA Labs