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

Search This thread

dronkit

Senior Member
Jan 14, 2013
61
22
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now, suddenly I find there's the no SIM indication, and in settings -> about phone it says IMEI: unknown, and in software information it says bandbase version: unknown.
The firmware version I used was exactly the same as when I bought it, A325MUBU2AUJ4, with the right csc (ARO in my case).

EDIT: after a couple reboots, the bandbase version now shows, but still no IMEI or SIM detected.

Can anyone help me? What happened? What can I do? Thanks in advance!
 
Last edited:

dronkit

Senior Member
Jan 14, 2013
61
22
UPDATE: it got unknown baseband againI

I relocked the bootloader and now in download mode I have an option to "show barcodes" pressing the side button. The barcodes show the right IMEI and serial number. Maybe stuff wasn't erased, just inaccesible by the rom?

I was told by a technician to flash the original ROM (already did) then root again. Tried several versions but not an older bandbase because downgrade is forbidden by the bootloader, apparently, to no avail. Would try a newer baseband but i'm afraid it will not work and will be unable to go back to the origial baseband version.

Weird thing is, there is the EFS directory but no /data/nvram or /dev/nvram
 
Last edited:

edukardo

Senior Member
Jun 16, 2013
446
185
Buenos Aires
Samsung Galaxy A32 4G
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.
 
  • Like
Reactions: dronkit

dronkit

Senior Member
Jan 14, 2013
61
22
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.
How did you root it?

as I understand, after rooting, warranty is void since it implies flashing a magisk patched boot image or AP tar. In my case I was indeed able to relock the bootloader and flash the original firmware but upon entering download mode, it shows "warranty void 0x01".

was it the same in your case?
 

dronkit

Senior Member
Jan 14, 2013
61
22
Flashed original firmware, relocked phone, and then went to Samsung Office. I had no problem with it
most likely the warranty vod bit was on (you can check it yoursef by entering odin mode) and they didn't notice
so you got it fixed for free?
did they mention what did the fix consist in? I heard they say they change the motherboard, which is a lie, they just write the nvram or efs with the right stuff

ah sos de argentina? lol where did you take it? to a samsung store? I'm from neuquen and got it at musimundo, but here's a samgung store too
 

dronkit

Senior Member
Jan 14, 2013
61
22
myself i was thinking of waiting for an update which should be soon, lock bootloader, flash some official rom and pull off the cable so it gives an upgrade error and doesn't enter download mode, then take it to the store
 

dronkit

Senior Member
Jan 14, 2013
61
22
nope, went to samsung, got rejected cause warranty bit on, no choice but take it to a service and I suppose they could do something with Chimera Tool, Z3X or something like that, which, as I've seen, claims to fix it in minutes (and the client gets charged handsomely, like 100 USD)

From Samsung I got the same bullsh*t I read in some threads: "this phone has been tampered with and it's a hardware problem, the board must be replaced"
 

dronkit

Senior Member
Jan 14, 2013
61
22
For the technically savvy, I got a strange Magisk log which kind of looks like it may be the problem. It seems to try to "unlock"* some devices on bootup but gets "permission denied". One of them may be the nvram or something like that. I have an EFS directory but no NVRAM directory anywhere or /dev/nvram.
 

Attachments

  • magisk_log_2022-01-27T06_42_15.log
    149.7 KB · Views: 44
Last edited:
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
 
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
or atleast use magisk with aug or even older firmware if you can... is your a32 A325M or A325F?
 

dronkit

Senior Member
Jan 14, 2013
61
22
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
what's JTagged?
 

dronkit

Senior Member
Jan 14, 2013
61
22
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
I did, I tried all combinations rooting/unrooting with the new magisk 24.1 the new version, A325MUBS2AVA1
It's a 325m btw
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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
    I registered here only to express my gratitude to you.
    If you could only imagine how grateful I am to you!
  • 7
    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
    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)
    3
    @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!
    1
    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
    I registered here only to express my gratitude to you.
    If you could only imagine how grateful I am to you!
    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.