I currently have Nothing Phone (2) with A13 (Android 13), NOS 2.4 which is the state the phone comes in after purchase in the shop.
If I update the Nothing OS firmware, I will get A16 (NOS 4.0).
To install /e/OS, i need to have A15 on my phone. Here is a warning from the wiki:
The required version is Android 15, which may be lower than the LineageOS version you are about to install - this is not an error!
If there are multiple updates of that version (e.g. security updates), make sure to use the latest!
If you need to upgrade or downgrade your device, please search online for guides.
We are unable to provide specific instructions here and on our support platforms.
A firmware update is also required.
Is it possible to do the following (I use Gnu/Linux):
Download this file separately => Pong_V3.2-250917-1451-image-firmware.7z
I long for the days of yore when flashing was a matter of copying a ROM to the SD card, rebooting in recovery, picking it from a list, and selecting âflashââŠgood times.
Since then, hereâs what Iâve learned in terms of flashing my Nothing Phone 2 (which yes, is indeed codenamed âpongâ, and is the ONLY phone codenamed âpongââŠa pox on whoever decided that âNothingâ and âPhoneâ were good ideas for company and product names)âŠ
For starters, nothing on your list looks like anything Iâve flashed in the past. Not saying youâre not on the right track for updating low level firmware, just that it doesnât look familiar at all.
some devices still offer this feature (Samsung and maybe others ?)
but you are right bootloaders are now locked, and sometimes trickies to unlock (Samsung and surely others âŠ)
I am sure that many users and fans of /e/OS will be happy that it is now possible to install e.s on Nothing Phone 2.
I hope this post will be popular))
Itâs also great that the forum and its users are so active and help each other!
As for blocking the bootloader, I agree with you, and I refused some Xiaomi models that are significantly better than Nothing Phone 2 in terms of technical characteristics and other brands, so as not to wait a month for permission from China and also not to give my mobile phone number to Chinese companies.
As far as I know, among modern phones, only a few companies allow the bootloader to be unlocked: OnePlus, Motorola, Nothing, Asus, and, oddly enough G@@gle))
As for my question, I cannot find the answer to one question in order to move forward.
I currently have A13, but I need A15 to install /e/OS. How can I update my phone to A15?
Tip: Before installing /e/OS on the Nothing Phone 2 Pong for the first time, install the latest stock OS version 15 build on the device
This will allow me to move forward.
I have seen information about using âpayload dumperâ for the payload.bin file located in FULL OTA. In this regard, I have a question.
@tom1995 , Iâm glad that official support has come for the NP2; Iâve been running Ronnieâs builds for about two years now (including the bad-old-days of A13 that caused incoming SMS messages to randomly get dropped without warning or error; so glad that got fixed).
In terms of the A15 requirement, Iâm tornâŠI went to /e/OS from A13 and have been on the update treadmill ever since (well, I stopped at 2.8 and Iâm waiting to just migrate to my 3(a)), but I didnât require an update of the main firmware when moving to a14 or a15.
So, I find myself in a bit of a quandary - I donât want to go against official documentation, but I also know that my personal experience tells me that I flashed from NothingOS based on A13 to /e/OS, and upgraded from there, without needing to go back to NothingOS in the interim.
Moreover, there seems to be a bit of a tricky quandary the documentation wants you to follow - NothingOS 4 is based on A16, so if youâre supposed to be on 15 rather than 16, thatâs a dedicated download. It looks like thereâs an archive of NothingOS 3.2, which is probably your best bet, and can be downloaded here:
Try flashing that first via the manual updater on the phone, and see if that gets you to A15 before you start flashing the /e/OS ROM as a part of the rest of the instructions.
This collection of sites and applications is also super helpful for this phone, and other Nothing phones in general; itâs worth the bookmark:
The main question now is how to switch from A13 to A15?
If youâre on NothingOS 3.2 already, youâre probably already on A15. If youâre not, it should be a matter of downloading the ZIP (the spike0n link sent me to the archive.org repo that is officially provided through Nothing directly, but either wayâŠgrab that 3.2GB zip file from wherever you want), then try doing a manual update from the phone directly in the settings>updates menu.
Am I correct in understanding that now I need to install FULL OTA (zip file) on my phone or is there another way?
Good morning Tom,
Unfortunately, I am stuck providing âeducated guessesâ here - as described, I moved my NP2 to /e/OS some time ago, so I can only combine my memory of what I did a year and a half ago, with my recent experience of flashing my NP3(a), and what the official documentation says.
The educated-guess comes from the documentation saying you need to be on A15, while acknowledging that attempting an OTA update of NothingOS will likely land you on A16. The logical consequence of these limits means that flashing a full ROM image of a known, intended version, is what seems to provide the greatest likelihood of success.
However, my NP2 is still my daily driver, and already on /e/OS, so Iâm not in a place to attempt an NOS 3.2 flash to provide direct confirmations regarding the success or failure of any particular set of procedures, Iâm afraid. Aftermarket firmware installation will always involve a good amount of trial-and-error; Iâm pretty sure everyone on these forums that didnât buy a phone from the Murena shop has gotten stuck in a boot loop at one point or another.
While I can appreciate the desire for confirmations prior to beginning the process, Iâm not sure youâll be able to get the kind of guarantees you seem to be requesting. There are very few folks who have the NP2, and fewer still that run /e/OS on it (my guess is that there are less than a dozen people in the world who fit that category). This isnât to dissuade you from joining me as an /e/OS-on-NP2 user, but what I am saying is that there is a point at which youâre going to have to take the plunge and attempt the flash, understanding that it may take a few attempts, and you may get your phone stuck in an unworkable state.
I would like to get a response from a user who has gone through this path
Iâll tag @cosphi , @s10n , and @TildeEth , since they participated in Ronnieâs unofficial release thread within the past six months and indicated that they were successful in flashing their phones. Obviously, I canât guarantee that theyâll be in a place to help (I will still stress that self-discovery and personal trial-and-error are requirements amidst the phone flashing community), but they may have some wisdom to share.
Thank you very much for your detailed answer and your willingness to help me!
Itâs definitely not my way ))
But what I mean is that there comes a point where you have to take the plunge and try the flash, knowing that it may take a few attempts and that your phone may end up in an unusable state.
I am in favour of getting an exact answer to my question, because I will also provide an answer if I have done something successfully.
It is simply not logical to give the user recommendations to take risks that could destroy his phone, which costs 300-500 euros.
In fact, I just need an answer to one question (it is above), everything else I can do myself without any problems.
And I believe that the answer to this question should be here, so that other users do not have to search for answers and take risks.
The next time you or another user buys a phone with an older version of Android, they will know what to do.
In addition, this solution can be added to the wiki, which will significantly improve it.
yes, you can flash âNothing Full OTAâ then e-3.3-a15
as pointed in post 2,
yes, you can also simply install e-3.3-a15
for the same result âŠ
so, answer to your question is both are possible⊠do it as you prefer
(i would not recommended incremental OTA, but may also do the job depending on your current situation â incremental is designed from witch point ?)
.
.
it is not the point here, just
DONâT TRY TO RELOCK THE BOOTLOADERâŠ
DONâT FLASH SOFTWARE DESIGNED FOR ANOTHER DEVICEâŠ
.
i will take some example to illustrate :
if you use the buggy eos web installer,
or even following official or good instructions, if you stop after the âwipe /system partitionâ step,
the phone will be
but if you apply the next step that is flashing /e/,
the phone will work as expected
