yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 2] PhantomApollyon:
FWIW - No issues here with uninstalling magisk, accepting the update to Beta 2, rooting by booting, and then direct installing magisk
[Nothing Phone 2] thisislukas:
Fair enough
[Nothing Phone 2] xtcislove:
2.5.0.BETA2 - Pong-U2.5-231102-1201-EEA

Magisk 26.4
[Nothing Phone 2] dlads:
Nice one... Shall I host it in the OP?
[Nothing Phone 2] xtcislove:
Yes thats why i posted it
[Nothing Phone 2] dlads:
Cheers will do now mate..

I'll patch it as well, will need a tester..
[Nothing Phone 2] dlads:
OP UPDATED:

stock and patched images added, thanks to @xtcislove for the stock image.

Stock: https://mega.nz/folder/XN8FBb6L#AAWx9LXDozuw9VBl2-fRag

Patched: https://mega.nz/folder/aN1yxA6J#BuyeAQuUR_Jz58tyqbmDXA

Patched with magisk stable v 26.4

👍🏼
[Nothing Phone 2] simdll:
Hi,

I installed the Nothing OS 2.0.4 update following your instructions. Everything worked correctly. Now I was wondering, for the next updates I have to do this process again, right? I didn't install Magisk in the inactive slot after OTA, should I do it? If I do this, will the next updates keep the root?

Thank you
[Nothing Phone 2] xtcislove:
Thats the way i do it every time and never had a problem. Usually i do the OTA for example to 2.0.4. Then i fastboot bot the patched boot.img from the patch before so in this case 2.0.3 and do a direct install from within magisk. This way i have a patched 2.0.4 active and a magisk backup from 2.0.4 to restore for the next ota.

A new OTA is written to the INACTIVE slot. So patching the inactive slot is useless.
[Nothing Phone 2] boontje3:
Yust tested working perfect, thx dit adding it
[Nothing Phone 2] dlads:
Perfect, thanks man 👍🏼
[Nothing Phone 2] dlads:
What @xtcislove just said.

You may get away with doing an update by way of installing the upstate, backing out then installing to the inactive slot, personally that fails for me so a full unroot is required.

In summary:

1 restore images in magisk, then install after ota

Or

2 full uninstall in magisk, boot patched image in fastboot

This should be in the op too 👍🏼

This bit:

Being rooted & Updating with an incremental update whilst retaining root

***NOTE: risky, doesn't always work, disable all modules before proceeding and reboot.

1. Open Magisk and select "Uninstall Magisk" then select "Restore Images"

2. Open settings / system / Software update and download the incremental update (will be substantially smaller than a full zip)

3. Once completed you'll see "Restart Now" do not click this, back out and then re-open Magisk.

4. Within Magisk, click "Install" then click "Install to Inactive Slot (After OTA)" Then click "Lets Go" your device will now reboot

NOTE* I've noticed that my device didn't boot after doing this and or the update didn't install, if this happens your device will more than likely eventually swap slots and then boot, i also noticed an issue with the update not actually installing after performing the above steps, so do so at your own risk, if this fails then you'd need to full unroot / full uninstall and restore images, then take the update and reboot.

On boot you'd need to reobtain a patched boot image and re-root manually.
[Nothing Phone 2] bertmag:
Does anyone have the stock recovery image for 2.531007-2102? I've got Orange Fox recovery installed, and I'm fairly certain that's why the update is failing even after restoring the stock boot image.
[Nothing Phone 2] dlads:
Think it may be in this thread (below) if not then you can pull it from a full firmware using fastboot enhance.

Thread '2.0.3 to 2.0.4 update issues with custom recovery [Solved]' https://xdaforums.com/t/2-0-3-to-2-0-4-update-issues-with-custom-recovery-solved.4639808/
[Nothing Phone 2] bertmag:
I appreciate it! I saw that thread, but it looks like it's for an older version and I would have needed to have backed up the original recovery.img, I'm still trying to pull/capture the new beta OTA.
[Nothing Phone 2] dlads:
Use the like button buddy 👍🏼 don't they have the recovery.img listed there?

I'll see if I can find it.
[Nothing Phone 2] dlads:
Here you go buddy.

This is from 2.0.3
[Nothing Phone 2] mullman85:
This Patch worked for my Nothing 2 on Beta 2. Thx!!
[Nothing Phone 2] dlads:
Thanks man, appreciate the feedback 👍🏼
[Nothing Phone 2] HippoMan:
I'm running 2.0.3 to which I upgraded after originally installing 2.0.2., and all of this was done following the steps outlined in the OT. In both cases, I installed the patched (rooted) image, also as described in the OT. Later when still running this 2.0.3 release, I manually switched from Magisk Stable to Magisk Delta, and that's the version of Magisk that I'm currently running in 2.0.3.

Now, I want to upgrade to 2.0.4, and instead of sticking with Magisk Delta, I want to simply utilize the Magisk Stable version that comes with the patched 2.0.4 image here.

Since Magisk Delta is different from the Magisk Stable that comes with the patched 2.0.4 image, is there anything special I need to do in order to upgrade?

I'm guessing that in this case, "Being rooted & Updating with an incremental update whilst retaining root" as described in the OP might not be safe, because of the differing versions of Magisk that are involved. Is that correct?

If so, I guess that it's safest to completely uninstall Magisk Delta and then just do the "Rooting by booting" procedure. But if so, will a "Rooting by booting" enhancement from 2.0.3 non-root to 2.0.4 patched-root still work?

I just want to choose the most reliable possibility for performing this upgrade.

What would be recommended?

Thank you in advance.
[Nothing Phone 2] dlads:
1. Unroot

2. Update

3. Install magisk 26.4

4. Boot the patched image

5. Directly install from magisk, once booted.

Done.
[Nothing Phone 2] HippoMan:
I thought it might be his simple, but I wanted to make sure.

Thank you!

PS: The hard part would be to re-root-enable all the literally dozens of apps that I currently have set up as root-enabled in the Magisk Delta whitelist, but I don't know of any shortcut for this, so I'll just probably have to bite the bullet and deal with this app-by-app.
[Nothing Phone 2] dlads:
Make sure to uninstall the delta magisk app
[Nothing Phone 2] HippoMan:
Oh ... one question:

You wrote the following ...

... but aren't steps 2 and 4 simply a single step, as outlined here in the OP? ...

If so, would the steps be as follows:

1. Unroot (includes uninstalling Magisk Delta)

2. Perform "3. Boot the magisk patched img" as described above

3. Install Magisk 26.4

4. Directly install from magisk, once booted.

Or am I misunderstanding something?
[Nothing Phone 2] dlads:
No mate, you need to update to 2.0.4 you cannot do that whilst you're rooted..

You could attempt to temp unroot by restoring images.

But I would recommend a full uninstall

The initial post I made is correct for your current scenario.
[Nothing Phone 2] HippoMan:
But in the text that I wrote, the very first thing I said (my step 1) is "Unroot". Doesn't that address what you're writing here?

Here ... I'll list the steps again ...

1. Unroot (includes uninstalling Magisk Delta)

2. Perform "3. Boot the magisk patched img" as described above

3. Install Magisk 26.4

4. Directly install from magisk, once booted.
[Nothing Phone 2] dlads:
I don't get you mate.

First things first you need to unroot, fully, get rid of magisk whilst you're at it.

Then update.

Then boot the patched image.

Then direct install.

You can follow that or do it your own way, your call man.

There are two types of unrooting, temp (restore images) or full unroot.

Additionally you can remove the magisk app as you'll be using another version 26.4

I can only tell you what I know works.. strictly speaking it makes no difference, it's just an image and your only booting it.

PS: step two, you missed updating, you're on 2.0.3 you need to update to 2.0.4
[Nothing Phone 2] HippoMan:
I'm asking this simply because I'm still confused about *your* instructions. Could explain what you mean by "Then update" and how that differs from "Then boot the patched image"? ... since those seem to be one, single step, as follows, which comes from what you wrote in the OP:

Could you explain how the "update" step you mention is different from the "Then boot the patched image" step that you mention?

Thank you very much.
[Nothing Phone 2] dlads:
You're currently on 2.0.3 right??

You need to go from 2.0.3 to 2.0.4

1. Unroot (entails removing the magisk app)

2. Take the update to 2.0.4

3. Install the 26.4 app

4. Boot the patched image (2.0.4 Is in the op)

5. Install directly via magisk

Done
[Nothing Phone 2] HippoMan:
Thank you.

How does "2. Take the update to 2.0.4" differ from "4. Boot the patched image (2.0.4 Is in the op)" ?

In step 2, are you referring to the NON-patched 2.0.4 image?

PS: Oh! ... In step 2, are you referring to taking the 2.0.4 OTA from within Android itself?
[Nothing Phone 2] dlads:
What do you mean mate? Booting an image is not updating anything.

A boot image is 96MB an update is over 2GB when collated.

If you wish to update to 2.0.4 booting the 2.0.4 boot image will do nothing at all.

Updating and booting an image are not the same thing..

The boot.img a very small part of the entire system, it's what we use to root the device.

PS I'm amazed you didn't know that.
[Nothing Phone 2] HippoMan:
So as I asked in my PS in my previous post, does "Take the update" mean "Accept the 2.0.4 OTA update from within Android"?
[Nothing Phone 2] HippoMan:
I have been doing many things involving ROMs and Magisk versions lately, and the word "update" can be used to mean different things in these differing contexts.

That's why I didn't know how *you* were using the term "update" here in your instructions.

If you indeed are talking about to taking the 2.0.4 OTA update from within Android, then I now understand what *your* meaning is.
[Nothing Phone 2] dlads:
Well tbh mate if you update to a new firmware then you should be updating your patched image to that exact firmware version too.

So updating should have one meaning and one alone..

You initially asked about updating to 2.0.4, that's the only thing I was referring to..

There is nothing else to update.
[Nothing Phone 2] HippoMan:
I totally understand this part and agree: "... if you update to a new firmware then you should be updating your patched image to that exact firmware version too."

But that's NOT what I'm asking about.

This is a communication or vocabulary issue between us, not a technical question. I want to understand WHAT EXACTLY I NEED TO DO IN ORDER TO PERFORM THE FOLLOWING: "Then update".

Whether I "should" or "shouldn't" understand is irrelevant. I simply DON'T understand what you are referring to specifically as "Then update" in your instructions.

I'll ask this a different way ... if someone told you to "Then update" in this exact, same context, what exactly would you ***DO*** ? What action or actions would you perform?

Thank you.
[Nothing Phone 2] dlads:
It's a case of common sense, you've asked me about updating to 2.0.4 from 2.0.3

You absolutely should know what I'm referring to when I say update.

Of course it's the actual system update being offered to you by your phone.

Look through all the messages I've ever received on this phone, the 10 pro, 8 pro, OnePlus 5 and Huawei p20 pro.

Nobody has ever mistaken what I meant by update? It's the firmware your phone is offering you.

Just follow what I've said and you'll be fine
[Nothing Phone 2] HippoMan:
You could have simply answered "Yes" when I asked you a few messages back specifically about whether this means an OTA update to 2.0.4 on the phone, instead of making condescending remarks.

But thank you for finally answering that question. This is indeed helpful.
[Nothing Phone 2] HippoMan:
But other people I spoke to just today used the word "update" differently regarding a different ROM upgrade. Your use of certain words in certain contexts can easily differ from some other people's use of those same words in the same context.

I don't know you well enough to have a clear understanding of every meaning of every technical term that you might choose to utilize. That's probably true about nearly everyone you will encounter in these discussion groups.

But I certainly know what you mean by "update" in this context now! :)
[Nothing Phone 2] dlads:
I'm not being condescending buddy, im just baffled as to how you don't know that I mean update your phones firmware.

Plus we've been talking all night about something that should be obvious ?

Either way, were on the same page now thankfully.

You should be good to go 👍🏼
[Nothing Phone 2] HippoMan:
Anyway, in case anyone is interested, I now know how I'm going to perform this switch from 2.0.3 with Magisk Delta to 2.0.4 with Magisk Stable. Here are the steps I will take.

(1) Take a full nandroid backup with the OrangeFox recovery that I have already been using.

(2) Connect USB and adb pull the /sdcard/Fox directory to my desktop computer, just in case things get massively trashed and I have to restore.

(3) Uninstall LSPosed modules and reboot.

(4) Uninstall all Magisk modules and reboot.

(5) Open up the Magisk Delta Manager and go into Settings=>Restore the Magisk app to rename the app back to its official package name and "Delta" name. I want to do that because I had previously done "Hide the Magisk app" when I originally installed Delta a few weeks ago.

(6) Reboot, just in case

(7) Open up the Magisk Delta Manager and select Uninstall Magisk and follow all of the steps it offers.

(8) When Magisk gets uninstalled, I assume this will ask for or trigger a reboot. Make sure that the reboot occurs, even if it means I need to perform the reboot myself.

(9) Go into Android Settings=>System=>System update and trigger the update to 2.0.4 . That will certainly reboot when it finishes.

(10) From my desktop, connect USB and do adb install Magisk-v26.4.apk , which I already downloaded from the official TJW site.

(11) With USB still connected, do adb reboot bootloader .

(12) Still with USB connected, do fastboot boot magisk_patched-26400_n1x00.img

(13) After the system reboots and comes back up, open up the Magisk Manager and do an install direct. I think this also reboots again when it's finished, but if not, I'll do the reboot.

(14) Configure Magisk.

(15) Then, take a lot of time to get Magisk to flag a number of apps as root. I need this because I use Tasker, and when it reboots, I had set it up to run quite a few existing apps, some of which need to be rooted. If any of these apps are not recognized as rootable at the time of Tasker boot-up, then the Tasker initialization will just fail. By doing this preliminary flagging of those apps as root, this will prevent that Tasker problem during the next system restart. I previous had a few dozen apps in the Magisk Delta whitelist. Since Magisk Stable doesn't use the concept of a "whitelist", I need to initially start each of them once manually so that Magisk presents the rooting dialog box for them. This is what I need to be doing during this step, at least for the apps which will run during Tasker startup. The rest of them can wait until I just manually choose to run them and the rooting dialog box appears.

(16) Reboot one more time.

(17) Take another OrangeFox nandroid backup. Then, I will have a "before" and and "after" backup, in case I need either one.
[Nothing Phone 2] HippoMan:
Thank you for explaining!

Even "update your phone's firmware" can be done either by OTA flashing or fastboot-based flashing.

I've been using the PixelFlasher utility to work on another device of mine, a Pixel 7 Pro. In that software package, "update firmware" means "flash a ROM image file or an OTA image file". That flashing is handled by the PixelFlasher software itself, but the word "update" is used in this case, and we have to specify whether a full ROM image file or an OTA image file is being flashed. And that software package does that flashing via fastboot.

I was communicating extensively for the past couple days with that module's developer about some issues I had with the program, and the word "update" was always used by him when discussing the firmware flashing, none of which was done by a system OTA update.

So, I think you can now see why I wanted to be totally clear about what *you* meant when specifying "update", and your use of that term turns out not to correspond to the other person's use within a similar context.

Anyway, thank you again, and all's well that ends well!(y)
[Nothing Phone 2] HippoMan:
It turns out that uninstalling Magisk Delta under 2.0.3 before switching to Magisk Official under 2.0.4 requires a couple more steps than I originally thought. I've now added those additional steps to my "cookbook" ...

https://xdaforums.com/t/guide-unloc...t-images-model-a065-eea.4605979/post-89168374
[Nothing Phone 2] dlads:
Dude it really doesn't matter how you update, it's your business.

Just update.
[Nothing Phone 2] HippoMan:
In my latest message, I'm just explaining why I was asking for clarification about your use of the the term "update". Since someone else's recent use of that term confused me during our own discussion, there's no way that I "should" have known what *you* meant, and it's reasonable that I asked you about that.

And since you clarified that, all is well now.
[Nothing Phone 2] dlads:
Please stop spamming my thread.

It's done, just let it go
[Nothing Phone 2] HippoMan:
I started performing the steps specified by you. I first unrooted and got rid of Magisk Delta. That worked fine. Then I did the "Take the update to 2.0.4" step as discussed (i.e., take the OTA update from within Android). It seemed to download the update, but then it said "Couldn't update. Installation problem", and it gave no error message.

I repeated the same OTA update procedure from within Android, and it also failed in the same way: "Couldn't update. Installation problem", and no error message.

I'm going to try to understand the problem and try to fix it, and if I can indeed fix it, I'll report how I did so.

However, if I can't fix it, I'll just install Magisk Standard 26401 directly into my 2.0.3 OS and forget about 2.0.4.
[Nothing Phone 2] ffejy462:
You're going to have to revert to stock recovery. I believe in one of the previous messages, you mentioned that you were using orangefox....

Before any questions are asked, please keep in mind that the homework is yours, and preferably done before making any modifications.

To keep it simple, to take an ota: return to stock, take ota, confirm good boot, then modify.
[Nothing Phone 2] HippoMan:
Oh, never fear ... I refuse to ask any more questions in this particular thread. I'm just reporting what happened, and the post you're responding to is just one such report.

And given that I didn't ask for any help, I very much appreciate your unsolicited and helpful explanation about getting back to stock recovery. Thank you very much.
[Nothing Phone 2] ffejy462:
I'm using stock recovery, but I'll bet there's some direction in the orangefox thread. Or you might be able to extract it from the full firmware zip, then flash with fastboot. Either way I wouldn't know the exact steps offhand without searching... Good luck
[Nothing Phone 2] HippoMan:
Thank you again, very much, for your unsolicited help!

My report:

As it turns out, I'm just giving up on 2.0.4, because it's not worth the trouble, and I don't have a lot of spare time to do all the necessary investigation about restoring the stock recovery.

Instead, since I already uninstalled Magisk, I'll just be installing Magisk Alpha on my 2.0.3 OS. My main purpose for this exercise in the first place was to get rid of Magisk Delta and install either Magisk Standard 26.4 or Magisk Alpha 26.4. Since we have a 2.0.4 patched image here with Magisk Standard 26.4, I thought it would be easy to get Magisk Standard 26.4 simply by doing what's necessary in order to flash that 2.0.4 image.

But because of all the previous miscommunication nonsense, and also due to the time needed to deal with the current recovery issue, this further effort isn't worth it for me. Also, I don't see anything about 2.0.4 that makes it any more desirable to me than the 2.0.3 version that I already have.

Given a choice between Magisk Standard and Magisk Alpha, I'm choosing Magisk Alpha.

I'll probably get around to doing this Magisk Alpha installation over the next few days.

End of report.
[Nothing Phone 2] HippoMan:
---------- quote removed ----------

I asked a question about a certain term you used, because I was confused about it. Instead of getting an answer, I got a lecture about how you believe I "should" know the answer. I asked two or three more times and just got the same kind of lecture again and again until *finally* you actually decided to answer my question.

I have no reason to believe that the same kind of thing won't continue with future questions that I might ask, and I just don't want to go through that again. It's disrespectful, and it's a waste of my time.

Thank you for sharing the info about the recovery. The user @ffejy462 gave me the same answer a few comments above this one, and I was planning in my spare time to do more investigation about how to actually accomplish that. Your comment here points me to that information, and so now I know where to find the details about this, and that will save me time.

So, thank you very much.
[Nothing Phone 2] alecxs:
(some posts removed on request of author)
[Nothing Phone 2] simdll:
Hi, I tried to install Google Wallet on my Nothing Phone 2 with unlocked bootloader and root (with Magisk). I added my card, but it won't let me pay because it says my device is not secure. I tried installing the Magisk play integrity fix module and apps like Safenet check don't give errors. It can sees that the bootloader is unlocked? How can I solve it?

Thanks in advance

Simdll
[Nothing Phone 2] dlads:
Use the play integrity fix...

Bare in mind Google is clamping down on this from now on and will continue to be, so expect a lot of updates.

Remove the safety net fix from displax, if no longer works..
[Nothing Phone 2] dlads:
OP UODATED: safety net fix removed, play integrity fix added.

Safety net fix (no longer works, use Play Integrity fix)

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

Expect a lot of updates, personally I install AMM (Androidacy Magisk module) this will let you know when there's an update available, which are almost daily.
[Nothing Phone 2] vitaliy0017:
I'm currently on Magisk Delta and looking to completely reset my phone back to stock and relock the bootloader. Does anyone have clear steps on how to approach this? I've been looking through different threads but want to be careful and not end up with a brick. Thanks!
[Nothing Phone 2] xtcislove:
Uninstall all modules.

Uninstall Magisk from the App and RESTORE IMAGE

Do a factory reset just in case

Relock bootloader

What i would do:

Update to Android 14 Beta

Rollback to Android 13

Relock bootloader

This way you are really sure you have nothing left to build a brick
[Nothing Phone 2] vitaliy0017:
Thank you! Quick question, why would you update to 14 then rollback?
[Nothing Phone 2] dlads:
He's suggesting that so that everything is at stock from the rollback to 13 from 14.

Generally speaking you just need to revert anything you've changed..so in your case it's the boot image, being rooted means it was patched, that needs to be undone or youll brick your phone.

If you've flashed a custom recovery like orange or twrp then same goes for that, you'd need to flash the stock recovery..

Upgrading then rolling back would fix that, it's overkill but fool proof.

Personally I'd just full uninstall magisk then flash the stock boot image to both slots.

Then if you've used a customer recovery, flash the stock one too.

Then relock.