I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....
Issue resolved, thread closed, thanks.
So I just rooted my S6 for the first time, and I'm not very experienced in rooting. I used ODIN to download, and did as told in the website here at galaxys6root.highonandroid .com/galaxy-s6-root/how-to-root-galaxy-s6s6-edge-on-android-6-0-1-marshmallow/ This meant my phone has a TWRP custom recovery but a custom one made by ManhIT, and I was successful in rooting, just that each time in recovery I do a system reboot, it hangs there so I do a force reboot which leads back to the lock screen just alright.
Then I wanted to download Xposed Framework, so I followed this tutorial to download it on Marshmellow 6.0.1: android.wonderhowto .com/how-to/install-xposed-framework-android-6-0-marshmallow-devices-0166278/
youtube .com/watch?v=B3qbY2CWz5M
I did everything, downloaded Xposed Framework for ARM64 Marshmallow devices but had to find the latest version, v85 for it and this is where the problem started. I went to TWRP recovery mode, and went to flash the xposed framwork zip, and clicked system reboot (of course it hanged, so force reboot), and since then it always has been stuck on the Samsung logo screen. I went back to recovery mode, did a factory reset, wipe all data, format data, and it still gets stuck on the logo screen.
Please please please please help!!!!
UPDATE: A possibility of this problem is due to having "No OS Installed".
what I would do if I were you is:
1. Smart switch emergency initialization to restore phone to factory fw with sn of the phone (upper right corner in SS menu) (connect phone only when you are asked, otherwise it will say your device is not supported)
2. flash CF autoroot for that model https://autoroot.chainfire.eu/
3 flash TWRP downloaded from https://twrp.me/devices/samsunggalaxys6.html for that phone model
and see what would happen (offcourse I would check after each step if the phone can boot)
brenner650 said:
what I would do if I were you is:
1. Smart switch emergency initialization to restore phone to factory fw with sn of the phone (upper right corner in SS menu) (connect phone only when you are asked, otherwise it will say your device is not supported)
2. flash CF autoroot for that model ]
3 flash TWRP downloaded from for that phone model
and see what would happen (offcourse I would check after each step if the phone can boot)
Click to expand...
Click to collapse
I fixed it already! I think what it was in the end was the lack of OS. Should've backed up my data before doing anything funny. Installed my OS again and bam my phone is up and running again :good: (had to delete the URL from this reply as I'm just a junior member)
Hey guys,
I tried to root my S6 yesterday - so I entered Download mode and flashed TWRP onto it. I ran into the known problem with android replacing the recovery app, so i disabled the auto restart in Odin, and voila - I had twrp access. Couldnt get SuperSU onto the device because Im using full disk encryption (havent solved that yet) - and I couldnt get past ADB sideloading the SuperSU thing. Anywho - I tried a few (compatible) TWRP images - and all of a sudden, I am unable to boot the phone, nor enter download/recovery mode
Its stuck on the Samsung Galaxy S6 boot screen, with a little red text saying "Recovery is not seandroid enforcing" Power+home+vol down boots it into the same state, and power+home+vol up doesnt do anything.
Edit: I got it into download mode by following guide on https://forum.xda-developers.com/s7-edge/help/recovery-seandroid-enforcing-t3416719/page2 .
Erh, not entirely solved - it still wont boot. Stuck in a boot loop. I can access TWRP now - but as the "SDCARD" is encrypted (and i cant see any option to decrypt it!) - i cant really fix anything.
Would it be an option to flash stock recovery? (And where do I find that? I see that other people are having problems finding that as well)
I found https://forums.oneplus.net/threads/encrypted-phone-and-now-cant-use-twrp.117119/page-2 - which suggests that TWRP should be able to handle an encrypted volume..so why isnt it prompting for decryption password?
ad9fe7uhasf said:
Erh, not entirely solved - it still wont boot. Stuck in a boot loop. I can access TWRP now - but as the "SDCARD" is encrypted (and i cant see any option to decrypt it!) - i cant really fix anything.
Would it be an option to flash stock recovery? (And where do I find that? I see that other people are having problems finding that as well)
I found https://forums.oneplus.net/threads/encrypted-phone-and-now-cant-use-twrp.117119/page-2 - which suggests that TWRP should be able to handle an encrypted volume..so why isnt it prompting for decryption password?
Click to expand...
Click to collapse
It won't boot it up even when you flash stock recovery. Because you messed up dm-verity.
If your device SM-G920F;
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: XEF
Auto: Selected
Manual: Unselected
Binary Nature: Unselected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download full firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this; (even if you have another one)
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press AP and select file which starts with G920 from downloaded (from Samfirm) and extacted zip folder.
Connect your phone to your PC in download mode (the "Downloading..." screen) and click "Start" on Odin.
When you see "PASS" text on Odin, disconnect the cable.
This method will reflash and update the firmware of your device WITHOUT messing any personal data on your device.
forumber2 said:
It won't boot it up even when you flash stock recovery. Because you messed up dm-verity.
If your device SM-G920F;
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: XEF
Auto: Selected
Manual: Unselected
Binary Nature: Unselected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download full firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this; (even if you have another one)
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press AP and select file which starts with G920 from downloaded (from Samfirm) and extacted zip folder.
Connect your phone to your PC in download mode (the "Downloading..." screen) and click "Start" on Odin.
When you see "PASS" text on Odin, disconnect the cable.
This method will reflash and update the firmware of your device WITHOUT messing any personal data on your device.
Click to expand...
Click to collapse
Amazing!! Thank you so much - no one else has mentioned that beautiful utility (Can I buy you a beer?) Ive managed to make it boot kinda normal again - but I think the image isnt quite right - there are constant popups with "IMS Service has stopped" and "com.sec.epdg has stopped" which renders it pretty much unusable. Ive tried clearing the cache partition.
ad9fe7uhasf said:
Amazing!! Thank you so much - no one else has mentioned that beautiful utility (Can I buy you a beer?) Ive managed to make it boot kinda normal again - but I think the image isnt quite right - there are constant popups with "IMS Service has stopped" and "com.sec.epdg has stopped" which renders it pretty much unusable. Ive tried clearing the cache partition.
Click to expand...
Click to collapse
I think you should backup everything you can and wipe data from stock recovery.
forumber2 said:
I think you should backup everything you can and wipe data from stock recovery.
Click to expand...
Click to collapse
Yes - definitely! But As the popups are appearing ALL the time (its practically impossible to use the device) - Its close to impossible to enter Private Mode to extract data. You seem to know a bunch
I have tried connecting a physical keyboard to enter private mode password - no luck. The popup ruins most input fields or cancels them. Tried working with adb, but I dont think theres a way into private mode?
As the device is not rooted, I dont think I can copy the private data folder away from the device via the shell. Safe Mode didnt help either - they keep appearing...stupid popups
I have managed to do a adb backup of the device - but that does not include Private Mode data, right?
Any last minute ideas?
(also - im serious about the beer )
ad9fe7uhasf said:
Yes - definitely! But As the popups are appearing ALL the time (its practically impossible to use the device) - Its close to impossible to enter Private Mode to extract data. You seem to know a bunch
I have tried connecting a physical keyboard to enter private mode password - no luck. The popup ruins most input fields or cancels them. Tried working with adb, but I dont think theres a way into private mode?
As the device is not rooted, I dont think I can copy the private data folder away from the device via the shell. Safe Mode didnt help either - they keep appearing...stupid popups
I have managed to do a adb backup of the device - but that does not include Private Mode data, right?
Any last minute ideas?
(also - im serious about the beer )
Click to expand...
Click to collapse
Yes, ADB backup won't include private folder.
Can you tell me which CSC code seems active when you boot into stock recovery?
Thanks for beer by the way, you keep it
forumber2 said:
Yes, ADB backup won't include private folder.
Can you tell me which CSC code seems active when you boot into stock recovery?
Thanks for beer by the way, you keep it
Click to expand...
Click to collapse
CSC code is NEE (Sweden?) (im danish though). It says - Appling Multi-CSC. XEF seems to be france. Could that be the reason?
ad9fe7uhasf said:
CSC code is NEE (Sweden?) (im danish though). It says - Appling Multi-CSC. XEF seems to be france. Could that be the reason?
Click to expand...
Click to collapse
I couldn't get it.
So, NEE was your original CSC code but now, it's XEF.
Am I right?
ad9fe7uhasf said:
CSC code is NEE (Sweden?) (im danish though). It says - Appling Multi-CSC. XEF seems to be france. Could that be the reason?
Click to expand...
Click to collapse
If this page is correct: http://www.all-things-android.com/content/using-private-mode-galaxy-s5 - if rooting the device is an option (that was all I wanted in the beginning, heh) - I could just copy the files out plain and easy.
ad9fe7uhasf said:
If this page is correct: http://www.all-things-android.com/content/using-private-mode-galaxy-s5 - if rooting the device is an option (that was all I wanted in the beginning, heh) - I could just copy the files out plain and easy.
Click to expand...
Click to collapse
You should root the device before encrypt the device
Ok, do the same procedure I've wrote above BUT in SamFirm, write NEE instead of XEF on Region Code section.
Let's see if this change will work.
forumber2 said:
You should root the device before encrypt the device
Ok, do the same procedure I've wrote above BUT in SamFirm, write NEE instead of XEF on Region Code section.
Let's see if this change will work.
Click to expand...
Click to collapse
Hi again.
The reflash didnt work. Im gonna see if I can find a rooting guide that actually works. When rooted, I should have access to all data. And after root, Ill reflash with LineageOS and start from scratch.
UPDATE: I followed the guide on https://www.tomsguide.com/us/samsung-galaxy-s6-guide,review-2856-3.html . It seemed to work until the first boot:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You nede to reset your device to factory default settings. THis will erase all your data".
I then proceeded to follow your guide again - but it still did not boot. So I think I've hit the final brick wall :/
ad9fe7uhasf said:
Hi again.
The reflash didnt work. Im gonna see if I can find a rooting guide that actually works. When rooted, I should have access to all data. And after root, Ill reflash with LineageOS and start from scratch.
UPDATE: I followed the guide on https://www.tomsguide.com/us/samsung-galaxy-s6-guide,review-2856-3.html . It seemed to work until the first boot:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You nede to reset your device to factory default settings. THis will erase all your data".
I then proceeded to follow your guide again - but it still did not boot. So I think I've hit the final brick wall :/
Click to expand...
Click to collapse
You CAN'T root it after you encrypt the device. I think you messed up the data partition now.
If reflashing the firmware didn't work too, you have no choice but wipe the data.
Yup, I think youre absolutely right. I wish I had found that information before I began
Thank you so much for the help. We need more people like you in the community
If you mean "The reflash didnt work" as in there was an error flashing hidden.img, and if you simply want to regain access to your encrypted data, you may be in luck.
I found myself in the same exact situation. What I did was use 7zip to extract the .tar.md5 file, and use 7zip again to create another .tar file that didn't include hidden.img. Then, I simply used Odin to flash the new file. I made sure that the firmware I was flashing was the exact, same firmware that was on my phone before this happened. Just search on Sammobile.
The key to regaining access to your encrypted data was to simply have your system marked as "Samsung Official", which you can check by going into download mode and looking at "current binary". If it says Custom, Verification fails as far as I can observe. This is true even if stock recovery says that dm-verity is okay. As long as you modified your system somehow (boot and recovery are the only ones I've tested), verification fails.
Since I regained access to my data, I may as well backup everything and start from a freshly reformatted /data, since everyone says that one should root before encrypting.
Verification Failed
Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data
Click to expand...
Click to collapse
ad9fe7uhasf said:
Hi again.
The reflash didnt work. Im gonna see if I can find a rooting guide that actually works. When rooted, I should have access to all data. And after root, Ill reflash with LineageOS and start from scratch.
UPDATE: I followed the guide on https://www.tomsguide.com/us/samsung-galaxy-s6-guide,review-2856-3.html . It seemed to work until the first boot:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You nede to reset your device to factory default settings. THis will erase all your data".
I then proceeded to follow your guide again - but it still did not boot. So I think I've hit the final brick wall :/
Click to expand...
Click to collapse
Update: I found out that, if you do encounter the "Verification Failed" message, you don't need to flash everything with the fresh bootloader. Instead, flashing the stock version would work fine.
For example, if you flashed TWRP and encountered the verification failed message (read-only mode), then flashing the stock recovery solves the error message and you can boot.
I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Download the latest MM stock rom and try to bypass the frp lock.
lord_melchett said:
I recently bought an S7 and wanted to root. It's my first Samsung phone so the software is new to me so apologies if there is an easy answer. I (extremely stupidly) re-enabled FRP lock within Android after rooting (hoping that it was stop the unauthorised actions warning). This now means when i start the phone it states "Custom Binary Blocked by FRP lock" and would not boot in to Android. I've read some threads but the current situation is:
1) When i tried to boot it would not boot to Android and stuck at the first splash screen and warning. Whilst i had rooted i did not flash twrp so only have the stock recovery.
2) I went in to the stock recovery and did a factory reset and cache clear. No change.
3) I tried Smart switch and kies - no luck - both said un-supported device or hung on connecting
4) I went to the thread with the most recent stock download (Netherlands) and downloaded that. I tried to install that and it hung for about an hour. I disconnected and it now says "An error has occurred whilst updating the device software" and does not boot.
So i cannot boot in to Android, have no custom recovery and KIES/SmartSwap do not work.
Any ideas????!?!?
Click to expand...
Click to collapse
Flash latest nougat Stock rom from sammobile using The latest ODIN software. You shouldnt disable OEM unlock next time you root/install custom recovery to your phone or else this will happen again, and you'll have to flash stock firmware again.
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.
pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.
Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.