I bought my OnePlus Nord pre-installed from Murena in November 2021 and since then everything worked but I was only using OTA Updates and replaced the recovery with TWRP.
Then I noticed that there is already 2.6.3 available, but only a community version, so I tried to install this version via TWRP and created a backup of all partitions before installation:
Installation went well and it said it’s using unused Slot A.
Then after reboot, it started directly into the eOS recovery because it could not boot the system.
Using fastboot, I changed the Slot to B, rebooted and it started again with the old system.
And then I broke everything…
I switched back to Slot A, booted into recovery and tried to install the 2.6.3 community ZIP again via ADB sideload, which also I looked OK, but I didn’t realize that this now overwrites the previously working Slot B.
After rebooting again I ended up in eOS recovery, no matter which slot I used.
So I tried to install the old 2.4.1 version via ADB sideloading.
Long story short, my device is now bricked, I can enter fastboot mode but I don’t know what I can do to recover.
When I try to boot the TWRP image, I get “FAILED (remote: ‘Failed to load/authenticate boot image: Load Error’)”. (Image from here Download twrp-3.7.1_12-0-aviciiv2.img)
Same with eOS recovery.img from 2.4.1
I tried to flash stock ROM as described here but after fastboot reboot fastboot it sais “Failed to boot into userspace fastboot”
I installed everything for running the MSM tool and can connect to the device, but when I try to run it I always end up with the MSM error “device not match image”. I tried it with all images from here.
Now I’m pretty much lost and I don’t know what I can do.
Also I’m not sure which stock ROM do I actually need and whether I have a “Global”, “EU” or “India” version.
Which Version of the stock ROM do I really need?
I still have the invoice but it only describes it as: “Murena Nord 5G 128GB Grau - Grey Ash”
I ordered it in Germany, so I guess it’s the EU Version, but how can I know?
Any help is very appreciated.
Pardon, but with this installation confusion it’s a small miracle that you can still get into fastboot mode. Try one of the (not India) FastbootRoms files brought by @mauronofrio.
Unzip downloaded *.zip file and run: flash-all.bat (Mauronofrio Fastboot Rom Flasher)
You’re right and I have to admit that I was doing this for the first time actually. So beware with me .
Fortunately I was now able to start the eOS 2.6.3 recovery image and could then even boot the system which at least works in some parts (but no WLAN or USB File-Transfer possible. Bot cannot be enabled)
What I did was to “fastboot flash” ( some) images from the 2.6.3 community image (after extracting img files from payload.bin):
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot reboot fastboot <---- Last line that was executed, then waiting, but no connection anymore
fastboot flash abl abl.img
fastboot flash aop aop.img
(some more img files)
which returned:
Sending 'boot_b' (98304 KB) OKAY [ 2.399s]
Writing 'boot_b' OKAY [ 0.339s]
Finished. Total time: 2.831s
Sending 'dtbo' (24576 KB) OKAY [ 0.602s]
Writing 'dtbo' OKAY [ 0.069s]
Finished. Total time: 0.702s
Sending 'modem_b' (174796 KB) FAILED (Status read failed (Too many links)) <-- I did re-try this line later and then it succeeded.
fastboot: error: Command failed
< waiting for any device >
Sending 'recovery' (98304 KB) OKAY [ 2.280s]
Writing 'recovery' OKAY [ 0.464s]
Finished. Total time: 2.821s
Sending 'vbmeta' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_system' OKAY [ 0.000s]
Finished. Total time: 0.016s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
After “reboot fastboot” the device did show “fastbootd” in eOS recovery, but it was not detected on my computer. So I cancelled the script, rebootedt and it actually booted the e/OS System.
So it looks much better now than before.
From this point on, what would be the best approach to either make 2.6.3 fully working, or go back to 2.4.1 (community or stable). I don’t care what is running in the end if I have a fully working system again.
So you suggest to just follow the steps described in “Steps to install /e/OS from recovery”?
But then I’m still not sure whether I should stay with 2.6.3-t or use 2.4.1-s?
And is it actually possible to use 2.4.1-s after installing 2.6.3-t (because it is also and Android update from A12 to A13, right)?
Sorry, but since I’m not very experienced I’m very confused especially I cannot find much information about downgrading, only that it’s actually not intended.
Update:
Now running 2.6.3-t and everything seems to work so far, except WLAN/WiFi!
When I try to enable it, it gets disabled again after a few seconds, no networks are discovered.
Unfortunately WiFi this is the most important thing in my case .
I remember there was nearly exactly the same issue quite some time ago when I upgraded from 1.3 to 1.4 or 1.4 to 1.5 (or so). But that was a bug in eOS.
Any idea what I can do?
Is there a possibility to go back to 2.4.1-s (loosing all data is OK because I have a backup)? If, so, what exactly do I have to do? Installing 2.4.1-s via sideloading does not work anymore due to new Security Patch Level.
Have you checked that WLAN/Wi-Fi works with OxygenOS Stock Android?
Warning Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it will not work on /e/OS as well. Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
Well, it did at least work with 2.4.1-s.
Regarding Stock ROM I don’t know which version to choose, because I got the phone pre-installed from Murena. The procedure that is described here did not work. MSM always stopped flashing with “device not match image”.
If the bootloader is unlocked, it is not necessary to flash in EDL mode with MSM tool, but this also works very well with fastboot or if you have OxygenOS in *.zip flashable format via recovery.
@suud, you are flashing different custom recoveries/ROMs and don’t even know which ROM is based on which Android version and don’t inform yourself sufficiently, although the WWW has enough information about the OnePlus Nord 5G (avicii) offers. Pardon, but this is getting too sensitive for me. I’m dropping out here.
I’m just an average user who tried to manually update the phone software for the first time ever, which went wrong and now only wants to go back to a fully working system. I constantly crawled the www and read forums and articles for the past 3 or 4 days to get a better understanding of this whole “Android Custom ROM” area which is completely new to me and consists of a myriad of information, code names and so on which is really difficult to put together, at least to me and within a few days. I’m not doing this for fun or because I want to become an Android developer. I just want to fix my phone.
But thanks for your help anyway.
.
.
Warning