Nexus 6P (Angler) A15 Disponivel

Regain your privacy! Adopt /e/OS the deGoogle

Hello, a ROM for the Nexus 6P (Angler) running Android 15 was recently posted; I would love for an /e/OS version to be ported for this device.

I tested this version on my own device and it works well—even better than the standard LineageOS A11 version.

The link to the XDA page and the repository is right there; if anyone needs a tester, I am 100% available.

https://xdaforums.com/t/rom-15-unofficial-lineageos-22-2-for-google-nexus-6p-angler.4804733/#post-90778614

d mobile OS and online services

1 Like

Hello Ronnz98, thank you for always helping the community. I encountered this error during installation; I tried a few different TWRP versions, and I also got the same error when using the Lineage recovery.

did you follow clean installation instructions here:

https://xdaforums.com/t/rom-15-unofficial-lineageos-22-2-for-google-nexus-6p-angler.4804733/#post-90778614

You can also try to flash lineage ROM first and the /e/OS.

I applied all the patches and building went well.

2 Likes

The error E.1001 is about partition mismatch on the device. Did you fully follow all Wipe?

Following the install instructions exactly should be a fix. This would give clues GitHub - prodkt54/e1001-fixer: E1001 Fixer Fix Android ROM Error E1001 – Recovery & Boot Repair Tool · GitHub but probably not required.

1 Like

I followed all the procedures; I assumed this error was related to the partitions, given that I reinstalled Lineage 22 and everything went fine. I don’t think it’s an issue with how the ROM is built, but rather a lack of partitioned memory space required for the installation.

hmm, I did not change the partition sizes. Did you try to install the /e/OS-ROM over the lineage ROM?

1 Like

No, I performed a clean install! I followed the instructions for Lineage 22; I also tried installing another version of e-OS that you had created for the Angler using the same method, and I encountered the same error.

1 Like

ok, then I have no idea :upside_down_face:

1 Like

Are you aware that fail to update system image togerther with E 1001 would have a specific meaning in Dynamic partitions?

Please can you confirm whether this is a Super partition device.

Edit having studied the updater script in Ron’s ROM what I would try is simply take the recovery.img (which can be extracted with no special tools from within the ROM) and use this in favour of the Lineage recovery.img.

1 Like

I will test this solution as soon as possible.

I performed the test, installed the boot image for both Lineage and /e/OS, and installed the /e/OS recovery—yet, even so…

I found this, probably it helps:

https://xdaforums.com/t/question-error-e1001-failed-to-update-system-image-error-7.3782756/

1 Like

Hello friends, I managed to install the system.

I downloaded the latest version of TWRP available on the website, performed all the wipes, and created a recovery folder directly within TWRP.

I asked Gemini to put together a brief list of the steps I took:

Create the recovery folder: Go to Advanced > Terminal within TWRP and enter the command mkdir /cache/recovery to create the missing directory that the update script attempts to access.

Fix the file system: Go to Wipe > Advanced Wipe, select the data partition, choose “Change File System,” and confirm that it is correctly formatted as EXT4.

Use ADB Sideload: If you encounter read errors or corruption issues with large .zip files while installing the ROM from an SD card or internal storage, transfer and install the package using the sideload command from your computer.

In my case, the process got stuck at 71% in the command prompt (CMD), but TWRP indicated that it finished successfully without any errors. When I went to start the device, it showed a message saying no system was installed; however, I restarted it anyway, and the system booted up.

3 Likes