Question [fixed] rooted a325m suddenly no imei, no sim

Search This thread

dronkit

Senior Member
Jan 14, 2013
69
30
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?
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
 

dronkit

Senior Member
Jan 14, 2013
69
30
The issue is the exact same as this


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
 
The issue is the exact same as this


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
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
 

dronkit

Senior Member
Jan 14, 2013
69
30
FIXED! (working and stable so far)
Thanks to @Mighty_Rearranger
OK guys, I found a somewhat janky fix on another forum (I'm not sure if we're allowed to post links):

Root the phone, and, using Root Explorer or similar, delete the /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI/ folder. Reboot after that.

PD. You might want to remove Magisk after doing that, since IMEI disappears after you begin making calls again. You will lose root but your phone will be fully working again.

Edit: You can keep Magisk (and root) if you make the above mentioned directory read-only after it regenerates, but you will experience dropped calls from time to time. Data seems to work just fine.

From what I learned, it's a Magisk bug that happens with certain MediaTek processors. I don't think it'll be fixed in the forseeable future (the Magisk author closed the issue on GitHub without any explanation after almost a year without answer).
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
 
Last edited:

dronkit

Senior Member
Jan 14, 2013
69
30
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?
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.
 
  • Like
Reactions: TwilightxSaga

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    ikr! its so bug free and smooth and totally not filled with bloat that prompts me to install stupid games and tiktok when i setup my device everything :)
    Ik, and when you nand erase the firmware in odin and then the pc crashes mid flashing, then you must buy a new samsung phone because samsung likes money more than mr krabs does 😍😍😍,because samsung is a abbreviation of:

    S = Sh***y support
    A = Amazing modding community that you can install custom roms
    M = Members app which is XDA from wish
    S = Sh***y bloatware
    U = Ugly af ui design
    N = NVD_IMEI always fails
    G = GSI'S are preferred if your phone doesnt have a offical custom rom
    1
    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
    ikr! its so bug free and smooth and totally not filled with bloat that prompts me to install stupid games and tiktok when i setup my device everything :)
  • 10
    FIXED! (working and stable so far)
    Thanks to @Mighty_Rearranger
    OK guys, I found a somewhat janky fix on another forum (I'm not sure if we're allowed to post links):

    Root the phone, and, using Root Explorer or similar, delete the /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI/ folder. Reboot after that.

    PD. You might want to remove Magisk after doing that, since IMEI disappears after you begin making calls again. You will lose root but your phone will be fully working again.

    Edit: You can keep Magisk (and root) if you make the above mentioned directory read-only after it regenerates, but you will experience dropped calls from time to time. Data seems to work just fine.

    From what I learned, it's a Magisk bug that happens with certain MediaTek processors. I don't think it'll be fixed in the forseeable future (the Magisk author closed the issue on GitHub without any explanation after almost a year without answer).
    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
    7
    @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!
    5
    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)
    2
    ikr! its so bug free and smooth and totally not filled with bloat that prompts me to install stupid games and tiktok when i setup my device everything :)
    Ik, and when you nand erase the firmware in odin and then the pc crashes mid flashing, then you must buy a new samsung phone because samsung likes money more than mr krabs does 😍😍😍,because samsung is a abbreviation of:

    S = Sh***y support
    A = Amazing modding community that you can install custom roms
    M = Members app which is XDA from wish
    S = Sh***y bloatware
    U = Ugly af ui design
    N = NVD_IMEI always fails
    G = GSI'S are preferred if your phone doesnt have a offical custom rom
    1
    Same happened to me.
    I tried everything I could think of to get the IMEI back and couldn't.
    It was still under warranty and I took it to Samsung.
    Before taking it I unrooted it and locked it again.
    They fixed it for me with no problem.