yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A32 4G] applesucksLmao:
very strange, i guess we gotta not use magisk until its bug fixed.. i have seen other people have the same problem too, but anyways, i sent my phone to get probably JTagged for 54 us dollars, if they fix it well, great right, but if they dont i guess ill have to buy another motherboard from samsung or go to another city... and the best part is that while my phone is there, im using an S4 mini from 2013 with custom android 11 rom hehe
[Samsung Galaxy A32 4G] applesucksLmao:
i saw that auh firmware causes empty imei in another thread and to flash aug, maybe you could try this? https://xdaforums.com/t/has-anyone-successfully-rooted-this-a32-4g.4326193/post-85788523
[Samsung Galaxy A32 4G] applesucksLmao:
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
[Samsung Galaxy A32 4G] applesucksLmao:
well, your firmware is A325MUB"U2"AUJ4 and that means u cant downgrade to older versions that have binary1 so maybe you could try using samsung's new version which was released past month
[Samsung Galaxy A32 4G] dronkit:
what's JTagged?
[Samsung Galaxy A32 4G] dronkit:
I found it impossible to downgrade, download mode doesn't allow it. Couldn't find a tutorial to do it either.
[Samsung Galaxy A32 4G] dronkit:
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1

It's a 325m btw
[Samsung Galaxy A32 4G] applesucksLmao:
not exactly jtagged as my phone isn't "bricked", but the guy will probably use chimera or that other software from z3x
[Samsung Galaxy A32 4G] applesucksLmao:
yeah, probably not fixable that easily... have you tried to repartition the phone on odin using the pit file? https://samsungfirmware.net/how-to-use-pit-files-on-odin-for-flashing-samsung-phones/
[Samsung Galaxy A32 4G] applesucksLmao:
@dronkit

try to do this video and follow method 2

https://canon12380.blogspot.com/2016/07/how-to-extract-db-file-from-stock-rom.html how to extract database file for the sn writer tool
[Samsung Galaxy A32 4G] dronkit:
not yet, i'm asking at the magisk support forum but no significant response yet
[Samsung Galaxy A32 4G] applesucksLmao:
by the way, @dronkit, how are you using 4g lol? I'm thinking of using my s4 mini to route 4g and calls to the a32 if the guys from the repair shop don't solve it
[Samsung Galaxy A32 4G] dronkit:
my old nice s7. Sadly, the screen is cracked, the back and the camera glass too :(
[Samsung Galaxy A32 4G] applesucksLmao:
wait what? then why did you buy an a32 lol? the s7 (ain't it?) is a much much much better phone and it's so pretty.. are you using it as the main phone or just to route 4g and calls?
[Samsung Galaxy A32 4G] dronkit:
even not considering the broken glass, back, and camera glass, the battery doesn't last much, only one camera... It was a flagship at the time, but now even the A32 beats it on processor, ram, storage, camera... and I couldn't afford an s20, not even an s10 lol
[Samsung Galaxy A32 4G] applesucksLmao:
lol my a32 was with a discount by the mobile carrier
[Samsung Galaxy A32 4G] dronkit:
The issue is the exact same as this

No signal on MTK A-only SAR with recovery mode Magisk · Issue #1801 · topjohnwu/Magisk

Magisk installed to recovery partition on a A-Only system as root mediatek device. The device has no signal, and no IMEI number. Wifi works. Tried all versions including stable/beta/canary/canary d...

github.com

It's an open issue on Magisk github from a while ago now on several Mediatek devices

confirmed in my case by reading dmesg log

so guys, let's register in github and enter the link to report it's happening on the a32
[Samsung Galaxy A32 4G] applesucksLmao:
bruh, that sucks so much... i was actually suspecting of this problem in MediaTek phones as I saw people with a22 and a32 5g version having the same problem
[Samsung Galaxy A32 4G] dronkit:
FIXED! (working and stable so far)

Thanks to @Mighty_Rearranger

In more detail:

PREPARATION

1) root your phone by patching the stock ROM with the magisk app, as per Magisk's installation instructions. Reboot, install the app and everything Magisk asks until it works fully.

2) install and get ADB working in your PC. I love this one which is super lightweight.

3) enable ADB on your phone by enabling the developer options, turning on USB debugging.

ERASING

4) open a CMD terminal on your PC as administrator, go to the minimal ADB folder and run

adb shell

you will be running a terminal on your phone

5) make it a root terminal by running

su

in the phone, Magisk should ask for root permission for "system", allow it

the prompt should now have a "#" in the end, indicating you are root

6) go to the folder in question

cd /mnt/vendor/nvdata/md/NVRAM

7) delete the NVD_IMEI folder

rm -R NVD_IMEI

the IMEI appears instantly, but just in case, do the reboot.

RECOMMENDED BACKUP

7) optionally, instead of deleting the folder, rename it

mv NVD_IMEI NVD_IMEI.old

and move the backup NVD_IMEI to phone storage so you can save it on your PC

mv NVD_IMEI.old /storage/self/primary

copy that folder to your PC using the usual windows explorer or whatever

then reboot

AFTERWARDS

after reboot maybe you'll like to turn on airplane mode just in case so the IMEI doesn't die again.

then, as the post says, you can uninstall magisk (use the uninstall button on the app!!)

or try to keep it maybe installing it this time on the recovery partition and only booting root for necessary setup keeping airplane mode just in case to prevent IMEI loss again (didn't try this though),

or, to try to keep Magisk you can do the following:

[EDIT: Magisk ppl say "latest canary builds maybe work fine" (I take it they mean you won't lose IMEI after recovering it, with no need to do the following steps, and you won't lose IMEI in the first place with these versions, but who knows)]

8) enter adb again and make it root and go to the folder as in steps 4-6

OPTIONAL BACKUP

9) optionally, backup the newly appeared NVD_IMEI folder

cp -R NVD_IMEI /storage/self/primary

and the copy will go to phone storage so you can take it to your PC

MAKE FOLDER READ-ONLY

10) do a

chmod 550 NVD_IMEI

the NVD_IMEI folder is owned by user system and the radio group. This command will make the folder readable but unwritable for those users. Only the root user will be able to undo this or write to the NVD_IMEI folder.

CLOSING UP

exit

exit

after uninstalling magisk/making the folder read-only, turn off airplane mode and start normal use
[Samsung Galaxy A32 4G] dronkit:
If it's the first time you root the phone and your IMEI hasn't died yet, I would quickly go to a root ADB shell and make the NVD_IMEI folder read-only as in steps 8 then 10

Probably would backup the nvdata, nvram, nvcfg, efs and persistent partitions using dd (maybe i'll do a guide soon)
[Samsung Galaxy A32 4G] applesucksLmao:
im gonna test this now! thanks!
[Samsung Galaxy A32 4G] applesucksLmao:
I LOVE YOU!!! THIS WORKEDDDDDD!!!!!!!
[Samsung Galaxy A32 4G] zachary3732:
Heyy I'm new to this whole thing.. what does "root your phone by patching the stock ROM with the magisk app" mean?
[Samsung Galaxy A32 4G] dronkit:
Refer to these instructions, especially the "samsung"section
[Samsung Galaxy A32 4G] TwilightxSaga:
Thank you for your help also. I just bought it and the last thing my brother said to me was "Bro do not mess up that phone!" so a huge thanks. Just one question if you or anyone else can answer after the calls are made the imei drops and comes right back in like 5 secs is that normal since it was changed to read only?
[Samsung Galaxy A32 4G] dronkit:
you're right, I see something like that after calls, but it's just for a second. I thought that was normal but maybe it isn't.
[Samsung Galaxy A32 4G] TwilightxSaga:
Well at least its working so again a million thanks
[Samsung Galaxy A32 4G] Holidi16:
Thank you very much man, my Samsung A12 with the same problem back to the normal 😄

But, the problem is not 100% fixed, still have a minor bug (the signal gonna lost after receive/making a call, must restart the phone to make it normal again), but that's okay, at least better than before

It's basic call, not WhatsApp call
[Samsung Galaxy A32 4G] dronkit:
as I told twilightxSaga earlier, in our case the signal drops for a second and comes back. Mine is an A32. At the moment I've no idea what happened at the first issue, or happens after the "fix". Will keep looking.

In your case, after erasing the folder, did you uninstall magisk? via the app? or kept it? made the folder read-only?
[Samsung Galaxy A32 4G] Holidi16:
Ooh okay

Btw I'm not delete the folder, but just backing up it

I kept magisk and make the folder read-only, because it, I can install good lock and its modules (except 3 modules, keyscafe, sound assistant and pentastic)
[Samsung Galaxy A32 4G] dronkit:
@TwilightxSaga and ppl

I've been tinkering and found the following:

Comparing the backup, the old (backup) NVD_IMEI folder contained 6 more files than the new NVD_IMEI folder (the newly created one after erasing the old one). I checked and the files still in the new NVD_IMEI are identical to the ones in the backup.

I've copied the missing files from the old backup to the new NVD_IMEI folder, changed their permissions to match the ones in the new NVD_IMEI folder, and it seems the short signal drops after a call don't happen anymore.

The missing files are:

CS10_001

CS12_000

FILELIST

IP07_000

IP12_000

IP21_000

So, soon i'll write a step by step tutorial to do that.

Hope you did backup the old NVD_IMEI folder before erasing!
[Samsung Galaxy A32 4G] Dalprax:
Seriously, ty for all!!
[Samsung Galaxy A32 4G] asskriss:
i've already updated to u3 this method is still work?
[Samsung Galaxy A32 4G] dronkit:
u3 in the a325m??
[Samsung Galaxy A32 4G] Algirdas.Benetis:
https://xdaforums.com/t/solved-suddenly-unknown-imei.4389357/post-86498015
[Samsung Galaxy A32 4G] TwilightxSaga:
@dronkit I unrooted my device i put it back to stock. However since it's not root can I still delete the folders NVE or so because although I put it back to stock I'm still losing signal.
[Samsung Galaxy A32 4G] dronkit:
yeah, no, you won't be able to do this fix unless you get root. Afterwards, you can unroot if you want.
[Samsung Galaxy A32 4G] TwilightxSaga:
Yeah i had it root remember but its too much factory resetting and settting up over again lol. But I still have my old NVE and the files u posted above none of them are in the NVE.old I have 3 in there.
[Samsung Galaxy A32 4G] dronkit:
weird! So you originally had only 3 files in NVD_IMEI ? are you sure you hadn't erased it before or something?

I guess if all or some of the files you have in the old NVD_IMEI are not in the newly generated NVD_IMEI you can try and copy them there, and match their owner and permissions and see what happens

but surely you'll need root for that
[Samsung Galaxy A32 4G] TwilightxSaga:
Will try it hopefully tonight
[Samsung Galaxy A32 4G] EuStress:
I registered here only to express my gratitude to you.

If you could only imagine how grateful I am to you!
[Samsung Galaxy A32 4G] Holidi16:
Hello

Do you have the tutorial to do this method now?
[Samsung Galaxy A32 4G] samsung_f22:
Hi,

I am stuck with very same issue with Samsung F22 (marketed in India, MTK G80 based, codename SM-E225F). I have rooted, unrooted and flashed back stock rom a dozens of times for the past few days to fix the temporary signal loss after ending a call. All this started as I just wanted to enable camera2api without knowing the consequences!

I have never used linux, but have tried to learn about (user, group), ls, cp, rm, chmod, chown, -R commands, which are needed to implement what dronkit is suggesting. Problem is I have little idea about which permissions/ownership to set for my phone. I also have no idea who should be user and group among system and radio inside files of NVD_IMEI

Just after rooting using Magisk 24's AP patch, entering aeroplane mode and logging in to adb as su, I can see NVD_IMEI folder has ownership 'system system'. However, this is 'system radio' if I use Magisk 23's AP patch instead.

Similarly, not all files of the NVD_IMEI folder have same permission in Magisk 23, one file IP03_001 has 'system radio' ownership whereas rest of them have 'system system'. However, in Magisk 24, this is not the case.

When I try to copy some specific old files (IP21_000) manually into regenerated NVD_IMEI folder, IMEI is permanently lost.

Is NVD_DATA possibly corrupt? Should I erase it after taking a backup, so that it regenerates and repairs itself like NVD_IMEI?
[Samsung Galaxy A32 4G] abbody:
Actually the same happened to me and what I did is :

1- deleting the NVD_DATA folder.

2 - Activate Aeroplan mode , it will take some time to activate then turn it off .

3 - delete NVD_IMEI .

4- reboot .

5- NVD_DATA will be generated again .

that worked for me and I hope it will do the same for you.

====== You can use X-plore apk it is easy to use than adb shell , just install it and go to configuration -->Root access--> Superuser mode which allows changes in read-only folders then you can modify read only folders and permissions . =======

and if you success in fixing signal drop don't forget to share with us.
[Samsung Galaxy A32 4G] samsung_f22:
1. Is your phone's network perfectly fine now (i.e. no 10 sec signal drop after ending a call)?

2. Did you also copy extra files of old NVD_IMEI into regenerated NVD_IMEI? If yes, how many files were there in total?

I am afraid I made a big mistake by removing it first root without taking any backup. After completely uninstalling magisk, flashing stock, relocking, unlocking, flashing root again I can get only 13 files (see photo). FILELIST also lists these 13 files only but I guess that list is also autogenerated.
[Samsung Galaxy A32 4G] abbody:
Same like you I tried to copy the missing files from the old NVD_IMEI folder to the new one and I lost the IMEI permanently and that because IMEI certification fail you can check that *#0011# , so to fix that I delete the NVD_DATA folder .

that restored the IMEI but the drop signal is still there .

see my old NVD_IMEI filelist
[Samsung Galaxy A32 4G] StickyFingers28:
@dronkit and everyone else.

I deleted the old nvd_imei folder, sim starts working, network is back , then when i make or receive calls the network drops completely for a few seconds ( sometimes drops in the middle of the call ).

I looked for the missing files(that were missing in the new nvd_imei folder) in my old nvd_imei folder but those weren't the same as yours.

I could only find

FILELIST

IP07_000

IP21_000

and others were different. However, i tried to move all the files that were in my old nvd_imei folder but not in my new one to the new folder, and the network totally broke again.

What files exactly to put in the new folder from the old one so that the occasional brief network drop stops. Please advice.
[Samsung Galaxy A32 4G] craaziik:
Will rooting affect me with imei? (my processor is listed on picture)

View attachment 5624987
[Samsung Galaxy A32 4G] samsung_f22:
IP21_000 is evil, it is solely responsible for permanent signal loss in my F22.

Just by removing it, signal appears again(if it doesn't, NVD_DATA has been corrupted too and you may delete whole NVRAM folder, reboot to regenerate it, and then apply chmod 550 on NVD_IMEI after reboot).

Once you make a call, system again tries to write a new IP21_000, unless you have already applied 'chmod 550 NVD_IMEI' (note that this permission also goes away after deleting NVD_IMEI). I have inspected (in hex editor) a few IP21_000 thus generated after each call, and they are NOT identical. Another important file IP03_001 that is rewritten after each call remains the same though.

My gut tells me that restricting write permission to NVD_IMEI is not the correct way to go. System perhaps needs to generate/write something to IP21_000 after every call to work smoothly. Maybe its writing errors due to something else being broken after root. But whenever we deny it write access, the modem crashes and restarts. But again, I am not a programmer, I wish experts could take over from here!
[Samsung Galaxy A32 4G] StickyFingers28:
very interesting find. So just to have more clarity about this, where do you stand at the moment with your phone's network. Have you done the same procedure as above to get your network to partially work ? ( does your network still totally break for a few seconds after a call ).

But if not, and you have got your network to work fully without any network drops, may I know how you achieved it and what I can do to achieve the same? Thanks!

(:
[Samsung Galaxy A32 4G] samsung_f22:
I

Testing on unrooted, stock reflashed F22 with a locked bootloader now, with WIFI on, mobile data off. Yes, most of the time still it breaks for 12 secs after call ends. But there is an important exception (may not be a true rule, just an erratic behaviour of the phone, this evening). For the follwing, check Settings->Connections-> SIM card manager.

Stage-1: I have only one SIM (say SIM1) in my phone, but due to corrupt NVRAM, phone also shows SIM2 in turned off state with unknown number and carrier.

Stage-2: I now turn on SIM2 and make a call, and disconnect. After restoration of signal, if I go back to SIM manager, SIM2 now becomes greyed out(No SIM card).

Stage-3: I make a call again, disconnect, come back after restoration of signal, SIM2 becomes active again, but this time , it is in a turned on state.

Stage-4: I turn SIM2 back off, it displays 'no SIM card inserted' message (although the network is fine, as it is coming from SIM1). SIM card manager now greys out both SIMs (displays 'No SIM' in both slots). However, network remains fine, making more calls again DOES NOT drop network, and DOES NOT change status in SIM manager.

Stage-5: I restart the phone. SIM card manager now correctly shows SIM1 and correctly greys out SIM2. However, after making a call, disconnecting, network temporarily drops again, and after restoration, coming to SIM card manager, I find myself back again in Stage-1.

Toggling Wifi/Mobile data/Airplane mode also might lead to different stages mentioned above. We now have to find what happens to IP03_001/IP07_000/IP21_000 at each of the stages assuming these stages also occur in a rooted phone(But I am currently unrooted).
[Samsung Galaxy A32 4G] dronkit:
like I said, in my case they were all these:

The problem with the "evil file" IP21_000 maybe, like @samsung_f22 proposed and I also discussed with him, you should not copy it and wait for it or other files to be created, without changing permissions on NVD_IMEI to allow it.
[Samsung Galaxy A32 4G] dronkit:
I'm surprised, I didn't know there were any samsungs with that processor brand. What model is your phone?
[Samsung Galaxy A32 4G] dronkit:
that's very interesting. You've made me check and actually, with "my" method, te NVD_IMEI folder is read-only to system and to radio, but that only means those users can see it, list its contents, but not create or delete files. However, I didn't change the permissions of the files inside, they are owned by system and the group system and their permissions are rw-rw----, so they CAN be overwritten by system. And actually HAVE BEEN overwritten by system. I have files with last modified date of today.

Honestly, since i did the two things i've had zero problems and never changed anything else, but,

-if you want to allow the user "system" and/or the group "radio" to create files, change the permissions of the folder to rwxrwx--- or rwxr-x--- (chmod 770 or 750 NVD_IMEI) respectively.

-have you tried to actually make the files unwritable? like, for each file in NVD_IMEI a chmod 550 ? (which I didn't)

-MAYBE what is needed is to delete NVD_IMEI like I said, reboot, maybe make a call, sms, an USSD code, and then see if new files were created, and then, if necessary paste missing old files, and only then restrict writing on the folder and maybe on the files

-maybe in my case I had zero problems after my "fix" cause Magisk was actually fixed and it doesn't break the imei anymore. I've updated it frequently and i'm currently on Magisk 24301 stable.
[Samsung Galaxy A32 4G] dronkit:
awesome!

[/QUOTE]

weird, no idea if it should be always the same or not, is your phone the A325M?

anyway my NVD_IMEI folder has user system, group radio, and originally was rwxrwx--- which I changed to r-xr-x---

and all the files inside currently are owned by system, group system. rw-rw----

maybe you could try changing that, or as I said before, do the procedure, reboot, make some calls and stuff, then copy what's missing, and only then restricting access, or maybe, don't restrict access at all, provided you have an up-to-date magisk

didn't happen to me, maybe then don't copy it and it will be created by system as it was suggested above by you (the permissions on the folder should not be restricted to allow that to happen)

honestly, no idea if it would be auto-restored. If you just rename it instead of erasing it you can try without consequences, you can always re-rename it
[Samsung Galaxy A32 4G] craaziik:
hi! im sorry for the VERY late reply but its a A325M
[Samsung Galaxy A32 4G] dronkit:
oh, i didn't know that was the processor. I was thinking Mediatek, which is the chipset.

If it's an A325M, it's just like mine. IDK if you will lose IMEI after rooting via patching an image file. But when it happened to me, this is the procedure that brought it back. Maybe you won't have any problems, since Magisk has been updated. Try getting the latest Magisk. I'm on 24.3 but i think there's a 25 beta.
[Samsung Galaxy A32 4G] craaziik:
i did use magisk before i knew this issue (i installed it when i got it in november 2021) so yeah i might use it again
[Samsung Galaxy A32 4G] Elkingb:
Thanks, great fixed 😉 i use root explorer, work fine again thanks
[Samsung Galaxy A32 4G] lucascage:
it worked very well for me too, thanks
[Samsung Galaxy A32 4G] Tharki-God:
any way i can keep the root and still have the imei?
[Samsung Galaxy A32 4G] dronkit:
as the instructions say, yes. You may try to change the permissions of the NVD_IMEI folder and keep magisk, or not. I'm not sure that caused any effect. Just use an updated magisk.
[Samsung Galaxy A32 4G] Sheepmister:
Hope you fix for non backup user because i didnt backup the old nvd imei
[Samsung Galaxy A32 4G] dronkit:
perhaps... only perhaps... the problem was the permissions. You could try to set the NVD_IMEI folder with normal permissions instead of the ones I recommended in my steps. Cause like I said earlier, IDK if that's really making a difference, or it just became stable by itself or by updating magisk.

I'd say reset the permissions of the NVD_IMEI folder to rwxrwx--- doing chmod 770 NVD_IMEI, then (or first) update magisk, maybe even uninstall (via app) and then install the latest magisk.
[Samsung Galaxy A32 4G] Franzyy:
Thank you so much, my A32 has mobile data again.
[Samsung Galaxy A32 4G] Captain_cookie_200:
my phone has a new wierd issue. USING A A325F here. calling messaging all works fine. but when i turn mobile data on and hit it or watch something or do a speed test my signal strength drops to zero as if i entered a no signal zone. then it comes back and it works for a while then it happens again. this keeps happening in a loop. i tried your method but i ended up nuking my nvdata folder hehe... but after a stock firmware flash it is back. but this issue still remains. it doesnt happen in any GSI ROM e,g, crdroid, phh's aosp or any other. just happening in the stock firmware itself? i am on the latest one for this phone. please if you have any tips i could try. i gave it another go your method but it worked but this time it still happened. what has happened samsung?
[Samsung Galaxy A32 4G] Captain_cookie_200:
@dronkit any idea on what happened here?
[Samsung Galaxy A32 4G] Franzyy:
Sometimes also got the no signal icon even after making "chmod 550 NVD_IMEI", then it works after a few seconds. it happens at random times.

EDIT: The IMEI shows all the time even after the signal got disconnected

Samsung has such amazing bugless software /s