Any plans to move the /e/OS build into official to?
I prefer it over Lineage, but no sideloading anymore sure sounds sweet 
1 Like
Later Edit [1] I cannot help then.
⌠sadly I cannot help myself from answering having lost and unbricked an Xiaomi with the error message your system is destroyed which at the time sounded horrendous but is logical.
Is this a hypothetical question? Is super_empty.img present in your ROM? You need two answers
-
XDA search Question super_empty.img includes in Post #1 âThe purpose of a super_empty.img is to flash it in bootloader mode which will reset the super partition to contain and empty set of default dynamic partitionsâ.
-
You ask âIf so, fastboot flash super_empty.img?â
Not quite, the syntax by example is
fastboot flash dtbo dtbo.img
partition source file
I like the image below from https://source.android.com/docs/core/ota/dynamic_partitions/implement
This is a priority to fix then ⌠this link is filed under âAndroid Studioâ but can be relevant for many distros https://developer.android.com/studio/run/device
Quote
sudo usermod -aG plugdev $LOGNAME
Groups only update on login, so you must log out for this change to take effect. When you log back in, you can use
idto check that youâre in theplugdevgroup.
The system needs to have
udevrules installed that cover the device. Theandroid-sdk-platform-tools-commonpackage contains a community-maintained default set ofudevrules for Android devices. To install it, use the following command:
apt-get install android-sdk-platform-tools-common
The above is quoted from Ubuntu, YMMV.
[1] For following readers there is Install LineageOS on Pong | LineageOS Wiki
1 Like
I habe no clue how to solve your problem, but you could think of installing MagisK. That offers tons of anti-spy and privacy options. I wrote a while topic to that here in the forum.
1 Like
Thank you everybody, I have succesfully installed /e/ on my Nothing Phone (2).
The solution? I have no idea. What I did differently from before? No idea. I have extracted the files from the image and flashed them but the recpvery didnât work. I used OrangeFox instead and this time it worked! Maybe 17 (or so) is the lucky number for tries 
Thanks!
3 Likes
Update for /e/OS-a15 3.1.4
2 Likes
bravo⌠thank you Ron!
1 Like
Huge thanks @ronnz98,
I progress slowly, but who knows? perhaps I could help you soon to maintain !
1 Like
Please see here if you want to be ROM maintainer
https://doc.e.foundation/rom-maintainer
1 Like
Got it installed and everything seems to be working great! Just one minor issue - vibration doesnât seem to be working for calls/notifications. Haptics work fine (ie key presses) but the phone doesnât vibrate at all when receiving a call or a notification. Any fix for this?
(Update: Mainly when phone set to vibrate)
Iâm planning on installing e/OS on my Nothing Phone 2 soon, and I will share my step-by-step instructions when Iâm done. I just posted one for the Razer Phone 2, let me know if that is the kind of instructions youâre looking for. Razer - Phone 2 - aura - Documentation Suggestions - #2 by LCARS
On the latest phones with A/B partitioning, do this:
- On your stock OS, run through the OTA updates until youâre on the lastest version
- Enable Developer Options and USB Debugging
- Connect your phone to your PC, start adb and grant permissions (cmd: adb devices)
- reboot to the bootloader (cmd: adb reboot bootloader)
- Copy and save the output of this command (cmd: fastboot getvar all) to Notepad or Word
- Anytime you flash anything, run that command and save the output.
- Look for the line that says current-slot. My NP2 just completed an OTA and itâs on Slot B.
- All the partitons that end with â_aâ are pre-OTA. You want both slots to be fully updated.
- Switch active slots (cmd: fastboot âset-active=a) Restart the phone, and run the OTA again.
- When youâre sure both slots are fully updated, you are ready to install the custom ROM.
- Unlock your phoneâs bootloader (will add the details for NP2 later)
- Flash both boot slots: (fastboot flash boot_a recovery.img, fastboot flash boot_b recovery.img)
- Boot into recovery, take note of the active slot, and (adb sideload rom.zip)
- Reboot into the bootloader before starting the OS! Make sure the active slot has changed.
- Boot into recovery again, make sure the active slot changed (adb sideload rom.zip)
- NOW you can boot up the OS and set up your phone.
Why go through all these extra steps?
For example, lets say you updated to the latest OTA, which contains updates for some of the radio and vendor partitions. You reboot to complete the update, and now youâre booting on Slot B. Then you decide to flash a ROM, but which slot did it get flashed to? Chances are you flashed to Slot A, which doesnât have the updated radio and vendor partitions. You enter recovery and try flashing the ROM again, but now youâve reactived Slot B, which has the factory boot/recovery partitions, and your phone wonât boot or has weird errors in the OS.
So whenever your flash partitions to a phone with A/B slots, make sure you do both at the same time. Otherwise youâll just send yourself into a spiral the could end up with your phone bricked.
2 Likes
Update for /e/OS-a15 3.2
2 Likes
great to see bump - is there any special flashing steps given the version jump, or just sideload is enough since itâs still A15?
1 Like
To update from previous version,
- You can sideload from the PC via recovery mode,
or
- You can use the /e/ android `âsettingsâ â system-updaterâs â âlocale updateâ feature from the phone itself.
Download e-3.2-a15-20251029-UNOFFICIAL-Pong.zip (eOSBuildsRonnz98)
the package failed âpackage is for product mh2lm but expected Pongâ ⌠?
I uploaded the wrong ROM and posted old Pong ROM, will upload current 3.2 version now again
phew⌠would be great to have new file - as this my daily device.
Now uploaded and ready for download, hopefully Pong will make it official soon
all good again⌠thank you Ron
1 Like
So, Iâve been remiss in keeping updated; think itâll just-work if I update to 3.2 directly from 2.8, or should I do some intermediate installs?
Update for /e/OS-a15 3.3