Nothing Phone 2 (Pong) for /e/OS-A15 3.01
e-3.0-a15-20250612-UNOFFICIAL-Pong.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/OtherSmartphones/e-3.0-a15-20250612-UNOFFICIAL-Pong.zip/download
Please see sources and install instructions including recovery here:
https://xdaforums.com/t/rom-official-crdroidandroid-11-3-6-04-2025.4729324/
Use it at your own risk!
Please support the developer(s)!
Just got it installed and running perfectly on my end. Thanks for your work!
Ok after a few hours I’ve discovered that the camera seems to be unoperable, somehow. I’ll try and catch the bug this evening.
Thank you for the warning! Please let me know how your bug search goes so I can either defer installing, or help with the search!!
the sources seems to be updated… I’ll do a new build hopefully with cam working
Current uploading, so in about 30 min you can grab it from sourceforge, will post tomorrow here
Well, I’ve spent about a day on it, and have figure out that the issue may not be fully with /e/, as I have tried reflashing NothingOS 3.0 with nothing more than a root access and currently the built in camera app works but any other application trying to access the camera stream fails, the camera HAL might be partially dead. Whether it’s a fault of the Nothing drivers, or the manipulations I have done trying to find a fix or workaround, I do not know yet. I’m investigating.
Please test this version, sources were updated:
Ok, on my end, I’ve managed to escalate the issue to the tech team at Nothing after a few days of back and forth with the after sales support team. I will recommend caution when proceeding with flashing the rom, do mind the instructions to the letter, as far as I’m concerned the issue comes from the latest firmware version from NothingArchive for Pong, no clue if it goes back earlier. As far as I am able to see, I noticed that the only application that has a working camera (com.nothing.camera, the builtin), is also the only one using the camera that has the SYSTEM_CAMERA permission and is registered as a privileged app. All other apps trying to use the camera only have at best the CAMERA permission and are not privileged, and it does seem that this permission issue is one of the causes of the breakage, the other being some hash table mismanagement on the CamX end of things. If there is an update from the tech team I’ll bring it here, and if they bring me a patch I’ll try and form a magisk module for it. In the mean time, it can be assumed that e3.0.1 a15 20250625, the latest build provided to date by ronnz98, is functional, as I have not found any issue that could be directly related to it, my issue is reproducible on a rooted version of the NothingArchive firmware.
So far a much better experience than the first build. Didn’t notice anything not working. Battery lasts much longer than previous one. Like 5-10 times longer.
Got no problems with the camera, mobile connections also more stable.
It’s been many unofficial builds now. Can we go for officials now .
?
The Nothing Phone (2) is now officially supported by Lineage!
https://wiki.lineageos.org/devices/Pong/
Latest build:
e-3.0.4-a15-20250728-UNOFFICIAL-Pong.zip
I have been so happy with Nothing Phone 1 and Ronnz’ build for it that I have bought a Nothing Phone 2. I am about to install /e/ on it and am curious to know, is there a way to keep/copy the ringtones, notifications and some of the style? Should I copy anything before wiping everything?
And again, Ronnz you are awesome!
Please, could someone, anyone, give a step by step list what to do, please?
I need to know where to get boot dtbo vbmeta and vendor_boot imgs
I got them from lineage, but it doesn’t work.
Tried recovery from lineage and now twrp. I can’t seem to get e installed.
Please could anyone tell me what to do?
Devices on super may not mount until rebooting recovery. To flash additional zips, please reboot recovery to switch to the updated slot.
I am at a loss. Can’t find a solution online that works.
try crdroid ones? also may be the ron sourceforge folder had some from back earlier?
another way might be to flash to earlier e/os versions at time of the former .img files and then upgrade to later e/os from there?
I couldn’t find anything that works, so I kept the lineage install for now. No advanced security, but also no microg and I can’t see what I’m missing. Have to admit, lineage is very clean and the battery lasts forever. I feel less secure though, without the tracker blocker.
It does feel like cheating though…
Hi guys,
I have tried everything.
I can’t get it to work.
Only possible to install lineage. But lineage does nothing to block trackers. I feel naked. I do have to admit the launcher is 100x better than /e/.
I keep getting the message “Devices on super may not mount until after rebooting recovery.” In ADB sideload.
Please why is it that people are happy to have installed this custom rom, but I can’t find a step by step? Why can’t I find the right boot.imgvbmet vendor_boot etc? Which files do I need and where can I find them?
The answers to these questions might be obvious to everybody, but me, but why can’t anybody recognize there are people who do need these answers?
I have finally gotten an orangefox to run on my pong, it offers the option “Unmap Super Devices”, will this do the trick or will I brick my phone?
The weird thing is, I am warned against using Orangfox on an a/b device, yet this OrangeFox was made for the pong device.
PLEASE can anybody give me some solid advice?
I have now come to see there’s iodé as well, which might have a better launcher, I have tried it too, same problem…
Try to extract them from the build itself …
Sounds like you should do more reading on Super partitions aka Dynamic partitions and “move fastboot into userspace”.
Loosely speaking, Dynamic partition allows certain partitions to be resized / respecified on the fly. If you present the device with a certain partition configuration, load a “new” Recovery, and this recogises that its “map” is incompatible then it is expected that the user can “move fastboot into userspace” – that is fastbootd and allow corrections.
It feels like i have been doing nothing but reading. That is my point, I would really like a step by step guide for those of us who don’t daily install custom roms, that’s all.
With roms for this phone often a super_empty.img is provided. Should I flash something with that super_empty.img? If so, fastboot flash super_empty.img?
I have read about it, but I do not understand it. Which is why the straw I hold on to is that function in OrangeFox.
I have used FastbootEnhance.exe to extract the files i was looking for. I have found a guide on how to extract the files but that is written for use under linux. I run linux on all my machines but can’t get adb and fastboot to work correctly on them.