yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 2] auris1993:
Im interested in flashing this rom, but i have question, what steps would be to update this rom, like flash official rom and flash NothingMuchRom, or this rom have everything in super.img and just need update this rom, and no firmware and etc from official rom?
[Nothing Phone 2] ffejy462:
Op is pretty detailed on install, but I'll pass on my experience.

Pre install would require 2.5.1 on both slots (or at very least on slot a (just to be transparent, I used beta 2)). Format data.

Instructions on how to do those two things would require homework and not rom specific, which, while at it, I'd recommend how to return to stock.

To install (including updates):

Download rom from site in op to PC.

Unzip.

Updates would not require formatting.

Verify slot a.

Flash super per op instructions.

Flash vbmeta per op instructions.

Reboot

Telegram channel in op is active and a good place for "immediate" assistance.
[Nothing Phone 2] arter97:
r8 is up.

(Re-uploaded: 20240108)

r8

Stable release based on 2.5.1a

Google Sans font changes redone to fix missing characters
[Nothing Phone 2] Kkjin:
r9] arter97 kernel for Nothing Phone 2 gat-i seolchihaedo munje eobsgessjyo?
[Nothing Phone 2] arter97:
r9 is up.

r9

Stable release based on 2.5.2
[Nothing Phone 2] seba1428:
possible to install r9 directly on stock 2.5.1 ?
[Nothing Phone 2] Kkjin:
!!! thank you
[Nothing Phone 2] dfogelstrom:
@arter97 , theoretically, if I'm on 2.5.2 stock with unlocked bootloader, I should be able to dirty flash r9 and then vbmeta with no complications...right?
[Nothing Phone 2] spike0en:
Data wipe is mandatory to boot to the system after flashing the provided vbmeta (besides super). Consider taking a backup before proceeding. For more queries join the support group. Goodluck!
[Nothing Phone 2] dfogelstrom:
Awesome, why does it work like that?

Best backup method?

I'm on stock everything 2.5.2 bootloader unlocked.
[Nothing Phone 2] pawelmiernik:
Because the provided vbmeta image turns off forced encryption (dm-verity) like it warns in the first post, booting an encrypted system will cause a crash. Formatting data removes encryption, this rom doesn't turn it on. Back up your media to a PC, or an external drive, or an online source. Backup your SMS with a paid sms backup app like sms backup pro, backup your media and chats in WhatsApp in the app, if you're spoofing a pixel device unlimited backup on Google photos then your pictures should be safe as long as the folders are selected for backup, you can use neo backup or swift backup for the apps. There is no single all in one back up tool that works well, I don't know why, the closest thing that I've used was the built in xiaomi MIUI back up tool on my poco phone, you simply selected what you wanted to back up and it spit out a file or folder for you to copy somewhere, it included everything, settings, apps, messages, media stored on your phone, you could even select specific folders and files, and it all restored perfectly, I don't understand why more manufacturers don't provide a tool like this backed into their software.
[Nothing Phone 2] dfogelstrom:
Thank you for the detailed explanation! The more you know....
[Nothing Phone 2] :
good job mate
[Nothing Phone 2] dfogelstrom:
Sorry for late reply..

So, if, again, stock 2.5.2, I can dirty flash r9 and flash vbmeta after and be clear to boot...as long as I flash vbmeta after super a9
[Nothing Phone 2] pawelmiernik:
You can't dirty flash, you're quoting the part that says data wipe is mandatory, why would you even ask? You have to "clean" flash if coming from stock. You can "dirty" flash if updating NothingMuch from a previous version to a new version.
[Nothing Phone 2] AlbertoDR:
The question is what does that even do? It seems pretty idle on my device, but it was one of the first features of this rom, so I'm curious to know what it is and what it does, and if it should be disabled.
[Nothing Phone 2] Parkourkid93:
Good day everyone, anyone got viper4android working on this rom? or is it affected by this 64bit only?

I've only tried the repackagedviper by programminghoch
[Nothing Phone 2] ffejy462:
Yes, using the reengineered version for 64 bit. Follow instructions on GitHub.

Edit: I should add not every feature is working as intended in the original viper, but they're (slowly) working on it

Releases · AndroidAudioMods/ViPER4Android

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com
[Nothing Phone 2] hijibiji:
are you getting any glitchy sound in wired earphones while playing music ?
[Nothing Phone 2] ffejy462:
Everything I have is Bluetooth
[Nothing Phone 2] kpirnie:
Just got my NP2 today! psyched! will likely be on this tomorrow lolol
[Nothing Phone 2] kpirnie:
Am I right in thinking that I have to EDL back to stock in order to get back to stock? Or did I just waste a ton of time?
[Nothing Phone 2] bLack_Q:
You just have to be on latest FW 2.5.2
[Nothing Phone 2] pawelmiernik:
Crashdump to stock = EDL back to stock with special cable? ROM to stock = fastboot stock rom and format data
[Nothing Phone 2] kpirnie:
There's no full 2.5.2 "rom". It's incremental. What sucks is, EDL is 2.0.2 version, and then need to incrementally upgrade to 2.5.2

Yep. Flashing the rom requires that... which is not what I asked lol
[Nothing Phone 2] pawelmiernik:
Full fastboot roms including 2.5.2, edl to 2.0.2 -> unlock bootloader -> format data in recovery -> fastboot 2.5.2 stock -> relock your bootloader. I've done it exactly this way to get out of my trouble, but then like three days later I unlocked the bootloader again.

Editing to add that if you do flashing unlock_critical and flashing unlock then fastboot roms install faster, the phone doesn't have to boot into fastbootd to flash critical partitions and the process is just a little faster from my experience.
[Nothing Phone 2] kpirnie:
Ah cool! I'd love to learn how he/she did those! :)
[Nothing Phone 2] pawelmiernik:
You can rip all the partitions from the phone using the edl tool. So after he updated his phone with incremental, he downloaded all the partitions, compressed them and included scripts to run to install them all back on the phone using fastboot.
[Nothing Phone 2] kpirnie:
Yeah, I did that too. Ended up confusing myself with the 7 "super" images though :)

I didn't even notice if there was a system_a or vendor_a partition tho... I'll check in a little bit :)

edit: yeah, no system or vendor... just super... guess means more research for me :)
[Nothing Phone 2] dlads:
Flashed this, coming from PA, had no idea how much I'd miss NOS.. if this phone didn't have the glyphs and the launcher with custom icons and enlarging options then I may not have but being back on NOS has been an eye opener of what I've missed...

This ROM in particular feels snappier and has just brilliant stamina, I also didn't think I'd like the dpi being so high but I'm getting used to it.

Superb work @arter97

Thank you 👍🏼
[Nothing Phone 2] dlads:
This ROM coupled with Arters kernel.

I'd been having issues, so I changed gym apps from Caliber to alpha progression.

This is the first day with the new app, all other usage is normal via my daily routine which barely changes.

Staggering battery life really..
[Nothing Phone 2] zozo932:
THANK TOU NOW I HAVE A CRASHDUMP MINIDUMP

i follow the step im on 2.5.2 bootloader unlocked, i go to the plateform tool, adb devices, reboot bootloader flash

fastboot flash super super.img

fastboot flash vbmeta vbmeta.img

now im bricked :) :) my phone bootlop on crashdump
[Nothing Phone 2] ffejy462:
Please reread op. Especially the disclaimer. Then the pre flash instructions including the need (or not) for wiping.
[Nothing Phone 2] zozo932:
I followed the instructions so if you tell me if I wipe at the end it's good there won't be a crash dump?

i try before dislab dm verity
[Nothing Phone 2] ffejy462:
I'm not taking responsibility for your device, but all of the pertinent information is in the op.

In my case, I formatted the data partition; as I always do flashing a different rom on any device.
[Nothing Phone 2] zozo932:
Please can you give the line code for the final step (wipe data) in adb !

thank you
[Nothing Phone 2] zozo932:
Wipe data/Factory reset through ADB

Basically this is my problem/ I have 200+ phones running stock Android that need to be wiped (in the Wipe Data/Factory Reset way) and then a new ROM installed with some additional apks. Currently...

stackoverflow.com

for the final step (wipe data) this line is ok ?
[Nothing Phone 2] dlads:
<Mod Edit> Quoted Post Removed

Easy on the Fs and Fs..

There's tonnes of people on this ROM, if you can't read correctly then ask.

FYI, this ROM dances on the stock ROM.

It's more efficient and just better.
[Nothing Phone 2] dlads:
@arter97 how could I add an extra font to this ROM?

This is flash able via magisk but it only works on XDA on your ROM whereas on stock it's fine.

Full dot matrix font.

PS: thanks @nakheel for fixing caps. 👍🏼
[Nothing Phone 2] Razor64:
terminate called after throwing an instance of 'std::out_of_range'

what(): basic_string::compare: __pos (which is 917456) > this->size() (which is 0)

Aborted

Get this error. On firmware 2.5.2.
[Nothing Phone 2] Nerd10:
...Not sure if it's the Pixelify module I'm using for call screening and other Pixel features, but is this intended? Might be due to device spoofing, unsure. Updates should be handled through flashing super whenever a new build comes out in OrangeFox recovery, right?
[Nothing Phone 2] dlads:
In what regard?

Where are you getting this error?
[Nothing Phone 2] arter97:
A major beta update is up: r10b1

This release contains a custom bionic (C standard library for Android) library.

The C standard library is responsible for pretty much all native code running on the system, so any change made to it can have a huge impact.

I'm not expecting this release to be unstable, but since a lot changed, I'm marking this a beta.

2 major changes were made:

- The LLVM Scudo memory allocator has been replaced to latest jemalloc's stable tag.

Scudo is security-hardened memory allocator that mitigates some of the memory-related security attacks. On the other hand, jemalloc is optimized for performance and it was used as the default memory allocator on Android from 5.0 to 11.

The jemalloc used in this build is based on 5.3.0+e4817c8. It's opened-sourced at https://github.com/arter97/jemalloc/tree/a14 and pending review at AOSPA: https://gerrit.aospa.co/q/topic:"uvite-jemalloc"

With this change, memory allocations and frees are taking 23.4% less time with 1.7% less amount of memory consumption.

On Android, jemalloc is now only used for Android Go, and it's also a much older version, so this is indeed a drastic change. Keep in mind that some poorly made apps can misbehave with this change, but I have not encountered any.

- AOSPA's arm-optimized-routines was used.

A major advantage from AOSPA is that our team member, Jake Weinstein (xboxfanj), optimizes assembly routines to make basic premitive routines such as memset/memcpy/memcmp/strcpy/strcmp and math functions such as exp/log/pow/sin/cos/tan to perform better. Just like the memory allocator, these are used everywhere too.

AOSPA merges latest Arm code, which comes with approximately 200 new commits.
[Nothing Phone 2] wiadrovit:
So apparently I've found a bug (did I?), where it's impossible to sync properly with VW entertainment system.

Not sure if there's anyone else who could reproduce it, but let me explain what the issue is all about:

My Golf Mk 7 is unable to read contacts from my NP2. it acts as if it 's importing them but after the process is finished, there are no contacts present on my car's display. It only says that there were no contacts available for import and that I should either try again or check if phone does not require additional permissions to be granted.

The phone isn't asking for anything, bluetooth connection works fine, at least in terms of audio. Here we reach the second part of the issue, which is IMO even worse.

As soon as I answer/make a call, the other party is able to hear me via car microphone for around 5-10s after which I become silent. If i switch to earpiece, everything works fine, If I switch back to car audio, then I can speak for another 5-10s.

What I've tried so far to no avail:

- Unpairing and pairing again (removing car from the phone's BT/phone from the car's BT)

- Factory reset

This was tested in two VAG cars, 2014 VW Golf Mk 7 and 2019 Skoda Fabia Mk 3. The problem was identical in both cars, both are equipped with MIB2 entertainment system though they differ slightly (manufacturer/software).

Unfortunately I was not able to test it with another car brand, so can't tell if it's only VAG-specific.

I was previously running r9 when I first realized that the problem was present, I then updated to r10b this morning hoping it might help, but unfortunately the issue is still there.

I've tested connection using my wife's Pixel 6 as well as an iPhone, in both cases everything worked perfectly fine.

I will be happy to provide some input if @arter97 is interested in troubleshooting since I'm not sure how many people might be affected (VAG owners, put your hands up ;) )
[Nothing Phone 2] genatax:
I have the same problem, my car is also from the Vag group. The error is reported to nothing, as far as I have been able to read in many forums, it has to do with the bluetooth drivers, and the way it has to communicate, in other cars that are not of the wolkswagen group works perfectly. It is a pity.
[Nothing Phone 2] wiadrovit:
That sounds as though it's the same on stock NOS, is it? I really didn't have a chance to check it since I've used stock NOS for like one day and was under impression that everything is alright.

If that's the default stock rom behavior, then Nothing has screwed up big time. Is there any kind of issue tracker on their end?

Thanks!

EDIT: Apparently it is:

https://nothing.community/d/6217-import-contacts-to-the-car-problem

https://nothing.community/d/2190-android-auto-failing-to-start-phone-2/34

@arter97 sorry for blaming this initially on you, my bad!

I wonder when (if?) Nothing will fix this issue. I am no dev myself so it's hard for me to figure out, but perhaps it's possible to replace the BT driver in the next builds with the 'generic' one used in AOSP?
[Nothing Phone 2] genatax:
If you have the Rom of artec and you know how to modify, you could modify the library version of the PBAP, just after buying the phone I was perfect in the car, after updating it, and wanting to see the photos of the contacts I unlinked it and I could no longer see the contacts.If you have the Rom, you could modify the library version of the PBAP, just after buying the phone I was perfect in the car, after updating it, and want to see the photos of the contacts unlink it and I could no longer see the contacts ...

The problem is of the infosystem of the VAG group....
[Nothing Phone 2] TomeG2kc:
Question:

If possible, how I can install this Much ROM into slot A, and how to install newest crDroid into slot B?

THX for patience 👊🏼.
[Nothing Phone 2] dlads:
Two ROMs at the same time? Why? You can only run one
[Nothing Phone 2] TomeG2kc:
To comparison. It's possible?
[Nothing Phone 2] dlads:
Parts of it are but two functional ROMs? No I don't think so mate.

Used to be a way years ago, there was a Dev who made a way, I can't remember his name, but he was one of the OGs.

I highly doubt it's possible now.. honestly it's best to just install a ROM, test what you want and make your assumptions.. then without restoring everything test another.
[Nothing Phone 2] TomeG2kc:
Yep, I'll do as you said. CrDroid and then Much ROM. Wish me luck. Any advice?
[Nothing Phone 2] dlads:
Nothing much ROM is close to stock with a load of tweaks under the hood.

From my testing, I installed a lot of ROMs for the NP2 and I always found myself looking back at the stock / NM ROM, reason being was mainly stability, the NOS cam and glyphs... Lastly the NOS launcher is actually brilliant, the custom icon support and folders is second to none, you won't find it anywhere and the battery coupled with Arters kernel really pushes what's possible on this device so where with other phones (OnePlus, Sammy) you're always looking over the fence, with the NP2 I found myself looking back and feeling like i was missing out.

That's not to say that there's nothing to like, there are a tonne of options and a lot of work has gone in, but the likes of PA, you can't even change the icons, which yea... I didn't like.

It's a taste thing really, apples and oranges.

If I was you I'd probably check the custom ROMs then finish on NM ROM... I'm pretty sure you'll miss stock, which for me is a first... Well done nothing, they've managed to do what no other company has done to me since androids inception.
[Nothing Phone 2] TomeG2kc:
Nice conclusions, thx.

Any technical tips? My NP2 is into stock now 2.5.2, bootloader unlocked, and want to check those 2 roms.

No Custom Recovery - do you recommend Orange or another? Or should I leave it and use bootloader's installation? It's simpler, I think? You know, I played around with Custom Roms and Custom Recoveries a long time ago, and I'm a bit rusty...
[Nothing Phone 2] dlads:
Yea I would avoid custom recovery unless you obtain a ROM that can be flashed using it.. PA has one, most are fastboot installs.. there's a script for it.

Double check with the OP for the installation method, it's pretty straightforward forward.

Dont root unless you're happy with the ROM you're on.
[Nothing Phone 2] dlads:
New update is out...are we best holding off flashing the new update until you update your ROM, or will it just work with 2.5.3? Assuming super image is very similar.
[Nothing Phone 2] Neisim:
How can I make sure I'm in the right slot before installing the ROM? Also, would be possible to use the official flash tool to get the stock image? Thanks!
[Nothing Phone 2] dlads:
I use Franco kernel manager it identifies the slot you're on
[Nothing Phone 2] ffejy462:
fastboot getvar all

This will tell you which slot (and a bunch of other interesting things)

fastboot getvar current-slot

tells you which slot only

fastboot set_active x

x=which slot you wish to use

Be careful. Most likely will not boot older/previous os

Unsure on the flash tool. Probably best to ask in that thread.
[Nothing Phone 2] Neisim:
Amazing, thanks for the replies! I guess it would be possible to use the Fastboot Enhance that @dlads mention on this thread, right? Also, to the people who's using this ROM: did you had to install the Play Integrity fix? Is it required? Thanks folks!

And yes @ffejy462, I got the confirmation in the thread that's possible to flash the stock ROM back!
[Nothing Phone 2] dlads:
Yep play integrity fix is always needed in my experience
[Nothing Phone 2] areallytinydot:
Thank you for your amazing work!

Could you please provide a way to start with adb enabled? Some of us need it to skip the annoying setup wizard.

[BYPASS] [Unlocked Bootloader ONLY] Nothing Phone 2 Indian SIM Setup Block

You need unlocked bootloader to bypass this protection! If you have locked bootloader, just contact Nothing Support for bypassing and unlock bootloader. How to bypass Nothing Phone 2 Indian SIM setup block (unlocked bootloader only) 1. Install...

xdaforums.com
[Nothing Phone 2] dlads:
So I have two NP2 phones with me, one white one black.

The black one is on stock, received the update today, temp unrooted and updated.

My one is on this ROM, attempted to temp unroot then update to 2.5.3... failed.

Has anyone else updated from the nothing much ROM?

I did ask a few days back but no one said anything...I'm assuming I'm not the only person on this ROM.

I do also have the arter kernel on both phones.
[Nothing Phone 2] kpirnie:
so... you tried to update to the latest stock directly from a custom rom?

SMH
[Nothing Phone 2] dlads:
Someone advised me I could.. there is no update path advised here.

Are you attempting to help? I asked before, no one answered, I advised what I did, now I'm getting sarcasm.

Recognised contributer? Contributer of sarcasm?

Well done on a pointless comment.

This ROM is barely custom, there are zero aesthetic changes to the stock ROM at all, changes are within super.img, so yes I tried to update..

This is one of the reasons why people prefer telegram and xda is dying.

Considering your shaking your head at me..

Tell me with all your infinite knowledge, how would you update? Because there isn't anything in the 9 pages here, besides if there's an update from the OP which is just a super.img... nothing regarding an actual firmware update from nothing.
[Nothing Phone 2] ffejy462:
I'd assume you'd need to return to complete stock rom, kernel, recovery, etc before updating. Then there's the potential of formatting data if it still fails.
[Nothing Phone 2] dlads:
Yea that's what I would do, I'd actually more than likely use the EDL tool for a clean slate.

Updating isn't obvious at all, which is why I asked...tbh if it's a full wipe every time then I'll just stick with stock
[Nothing Phone 2] ffejy462:
From like rom to like rom, just flash new rom (stock or custom), but if you change roms, even one based on stock, I would wipe.

I really don't know if you can go from arter's rom to stock and vice versa without issues, but it appears to not.
[Nothing Phone 2] dlads:
Yea of course, base change or ROM change id always full wipe.

If normal updates don't work then it'd be a stock flash then install NM ROM once it's updated.

Tbh the super image arter uses can be repackaged so it's a full firmware and flashed via fastboot, meaning every new update the ROM can be merged, would make life a lot easier, ATM we can't do that.

Tbh I'll probably end up just going to stock, too much of a pain to go stock, wipe then install this every time there's an update.
[Nothing Phone 2] ffejy462:
Or just stay on nm rom...He generally updates relatively quickly after nothing does. Granted, updating nm is a bit more time consuming vs stock, but worth it imo.
[Nothing Phone 2] dlads:
Might do, if it was just a full firmware then it'd be a lot easier.. tbh I like to get it early so I can update my root thread..

Haven't so far so will see what happens.
[Nothing Phone 2] arter97:
Built upon previous major update r10b1, a new update r10b2 fixes previous version's errors and merges NothingOS 2.5.3 update.

Camera, face unlock and TikTok should be now working properly.

It also contains new Adreno GPU drivers, coming from the stock's 615.74 to 676.56. You may notice a slight improvement in graphics performance.

(I tried using the latest and greatest 762.10 drivers, but it unfortunately breaks camera in Nothing Phone 2.)

Please keep in mind that r10b2 is based on 2.5.3, which means you must update your phone's other partitions to 2.5.3 prior to installation.

Follow https://github.com/arter97/nothing_archive .

I am not expecting any issues with r10b2 and I'll be marking it stable shortly if no unseen issues arise.
[Nothing Phone 2] arter97:
r10b3 is up.

This new beta update r10b3 should fix camera HAL corrupting some pictures.

The fix implemented r10b2 was limited to one camera daemon, r10b3 extends this fix to the camera HAL.

(I originally thought this was unnecessary but seems like it needs it.)

Please read the previous changelog as well.
[Nothing Phone 2] kpirnie:
so far so good mate. I think we have a winner ;)
[Nothing Phone 2] Anbiona:
After updating to r10b3 I have been having weird corruption issues with my images (see attached). It's happening at about the same rate as the images corrupting before the update
[Nothing Phone 2] arter97:
Yup, this is also a known issue and I have fixed it internally. It was due to the Adreno GPU drivers.

The stable r10 release will have the stock GPU drivers by Nothing.
[Nothing Phone 2] arter97:
r10 is now stable.

From the previous beta: The GPU drivers update was reverted to fix camera image corruption. There should be no camera issues. If there is, please report.