iMEI NULL, OEM Locked, RMM prenormal, NO Root. What should i do?

dinoonino

Member
Jul 13, 2019
6
0
0
Hello there, please help me :(
My A520F flashed with Resurrection Remix (Oreo) while I was using Nougat Stock ROM, then my IMEI was gone. So I flashed it again with RR (Nougat) and I could use Wifi but simcard didnt detected. I flashed it again with Stock Rom, Hades Rom and still no IMEI.
I didnt know about RMM state and KNOX before (because I used Lollipop and Marshmellow, not Samsung phone before) , so I flashed it over and over again, and then I was stucked. Root access was gone, efs corrupted, couldnt get into homescreen.
After tried any stock firmwre and method that i found, I could bring my A520F back to home screen with A520FXXU7CRHA XID and/or A520FXXU7ARJ1 (Combination Firmware), 'cant mount /efs' problem was gone but still NULL IMEI.


so now, this is my A520F condition :
1. IMEI (1,2,SV), Baseband ----- NULL (can't connect to internet or SIM card)
2. FRP lock : OFF, RMM state : Prenormal, KNOX void : 1.
3. I cant find OEM lock status in Download Mode screen, and I dont find it in developer option because my A520F barely flashed. I can't do the 'Date and Time' trick or waiting 168 hr for opening OEM unlock menu because my NULL IMEI and Baseband, NO Connection.
4. The only firmware that successfully made my A520F booted to home screen were A520FXXU7CRHA XID and A520FXXU7ARJ1 (Combination Firmware).
5. There was an error in recovery mode, which is said :
E: [libfs_mgr] Blob verification failed : 255
dm-verity verification failed...
E: [libfs_mgr] Error creating device mapping. Device or resource busy
[omc-app-link] fail to mount /system as rw

Other firmware installed resulting on error/no command bluescreen and I couldn't enter the home screen. I can't root it with OneClickRoot neither Kingroot.
I can't install Custom Recovery or Root because RMM state and OEM Locked. I've tried 'fastboot boot recovery.img' in adb command but no result, couldn't use fastboot command.

So.... what should I do? at least the first step for now to solve it....
 
Last edited:

moozer

Forum Moderator
Staff member
Jan 5, 2014
2,696
1,280
113
Bolton, UK
Hello there, please help me :(
My A520F flashed with Resurrection Remix (Oreo) while I was using Nougat Stock ROM, then my IMEI was gone. So I flashed it again with RR (Nougat) and I could use Wifi but simcard didnt detected. I flashed it again with Stock Rom, Hades Rom and still no IMEI.
I didnt know about RMM state and KNOX before (because I used Lollipop and Marshmellow, not Samsung phone before) , so I flashed it over and over again, and then I was stucked. Root access was gone, efs corrupted, couldnt get into homescreen.
After tried any stock firmwre and method that i found, I could bring my A520F back to home screen with A520FXXU7CRHA XID and/or A520FXXU7ARJ1 (Combination Firmware), 'cant mount /efs' problem was gone but still NULL IMEI.


so now, this is my A520F condition :
1. IMEI (1,2,SV), Baseband ----- NULL (can't connect to internet or SIM card)
2. FRP lock : OFF, RMM state : Prenormal, KNOX void : 1.
3. I cant find OEM lock status in Download Mode screen, and I dont find it in developer option because my A520F barely flashed. I can't do the 'Date and Time' trick or waiting 168 hr for opening OEM unlock menu because my NULL IMEI and Baseband, NO Connection.
4. The only firmware that successfully made my A520F booted to home screen were A520FXXU7CRHA XID and A520FXXU7ARJ1 (Combination Firmware).
5. There was an error in recovery mode, which is said :
E: [libfs_mgr] Blob verification failed : 255
dm-verity verification failed...
E: [libfs_mgr] Error creating device mapping. Device or resource busy
[omc-app-link] fail to mount /system as rw

Other firmware installed resulting on error/no command bluescreen and I couldn't enter the home screen. I can't root it with OneClickRoot neither Kingroot.
I can't install Custom Recovery or Root because RMM state and OEM Locked. I've tried 'fastboot boot recovery.img' in adb command but no result, couldn't use fastboot command.

So.... what should I do? at least the first step for now to solve it....
1 - Pull SIMs. Developer Mode enabled. Ensure 'Auto Update System' is disabled.

2 - Changed date to 4 weeks ago (turn off 'Automatic Date and Time')

3 - Check Software Updates (Check updates manually). Ensure 'Download Updates Automatically ' is disabled

4 - Reboot. Check for OEM switch in Developer Options

5 - Check date again (it's likely that the date will be current date, but if it is, just set it back to 3 days before last date change)

6 - Check OEM Unlock toggle is present. If not, go back and forth between the general settings tab and developer options and if needed use "close all" from recents and reopen settings again.

7 - If not working, undo all the above. Restart and try again.

8 - If it does work...celebrate - you can flash custom binaries and custom ROMs

9 - Get TWRP flashed through Odin
 
  • Like
Reactions: SnowFuhrer

dinoonino

Member
Jul 13, 2019
6
0
0
1 - Pull SIMs. Developer Mode enabled. Ensure 'Auto Update System' is disabled.

2 - Changed date to 4 weeks ago (turn off 'Automatic Date and Time')

3 - Check Software Updates (Check updates manually). Ensure 'Download Updates Automatically ' is disabled

4 - Reboot. Check for OEM switch in Developer Options

5 - Check date again (it's likely that the date will be current date, but if it is, just set it back to 3 days before last date change)

6 - Check OEM Unlock toggle is present. If not, go back and forth between the general settings tab and developer options and if needed use "close all" from recents and reopen settings again.

7 - If not working, undo all the above. Restart and try again.

8 - If it does work...celebrate - you can flash custom binaries and custom ROMs

9 - Get TWRP flashed through Odin
I really appreciate your idea sir, but the problem is i dont have any connection to network (simcard or wifi, because of the null imei), so the Check Software Updates is unusable.
And I can't flash TWRP because of OEM locked and RMM state prenormal :eek:
 

tekxilog

Member
May 20, 2020
11
2
0
Odin

Try Odin or Samsung Flash Tools! Its always helpful for me if that doesnt work try flashing twrp then a rom and changing the IMEI with root for root you can install magisk

---------- Post added at 10:32 PM ---------- Previous post was at 10:31 PM ----------

Wifi connectivity is might be because of the different files you flashes are not for the correct device it might be for A5 but different country
 

MaDaLiNoSt

Senior Member
Aug 15, 2013
795
275
63
Hello there, please help me :(
My A520F flashed with Resurrection Remix (Oreo) while I was using Nougat Stock ROM, then my IMEI was gone. So I flashed it again with RR (Nougat) and I could use Wifi but simcard didnt detected. I flashed it again with Stock Rom, Hades Rom and still no IMEI.
I didnt know about RMM state and KNOX before (because I used Lollipop and Marshmellow, not Samsung phone before) , so I flashed it over and over again, and then I was stucked. Root access was gone, efs corrupted, couldnt get into homescreen.
After tried any stock firmwre and method that i found, I could bring my A520F back to home screen with A520FXXU7CRHA XID and/or A520FXXU7ARJ1 (Combination Firmware), 'cant mount /efs' problem was gone but still NULL IMEI.


so now, this is my A520F condition :
1. IMEI (1,2,SV), Baseband ----- NULL (can't connect to internet or SIM card)
2. FRP lock : OFF, RMM state : Prenormal, KNOX void : 1.
3. I cant find OEM lock status in Download Mode screen, and I dont find it in developer option because my A520F barely flashed. I can't do the 'Date and Time' trick or waiting 168 hr for opening OEM unlock menu because my NULL IMEI and Baseband, NO Connection.
4. The only firmware that successfully made my A520F booted to home screen were A520FXXU7CRHA XID and A520FXXU7ARJ1 (Combination Firmware).
5. There was an error in recovery mode, which is said :
E: [libfs_mgr] Blob verification failed : 255
dm-verity verification failed...
E: [libfs_mgr] Error creating device mapping. Device or resource busy
[omc-app-link] fail to mount /system as rw

Other firmware installed resulting on error/no command bluescreen and I couldn't enter the home screen. I can't root it with OneClickRoot neither Kingroot.
I can't install Custom Recovery or Root because RMM state and OEM Locked. I've tried 'fastboot boot recovery.img' in adb command but no result, couldn't use fastboot command.

So.... what should I do? at least the first step for now to solve it....
Combination Firmware is used to reinsert IMEI Manually not to fix 'cant mount /efs' problem' !
Try reflashing latest stock rom using modded odin (do google search)