Do you have a IMEI issue or are you getting a DRK error?
This is either when your IMEI and/or Baseband shows Unknown (or a bunch of zeros) or you may be getting a DRK error when trying to boot your phone (sometimes even both).
This is caused by a missing or damaged EFS partition and can be repaired.
I am here to help. Some of you may have seen my guide over in the S7 forum which helps to fix this issue. Well, I plan on creating a similar guide for the S8.
In the meantime, if you are having any issues as mentioned above, please complete THIS FORM. Once I have received your form I will get back to you with information advising what can and cannot be done. I will then send instructions on how to fix your issue. This will also help towards creating my guide as it will give me some insight into the S8 EFS partition. As I do not have an S8 myself.
Related
This started with Flashing with wanam rom. I followed the instructions like always, and it was working, I was attempting to fix a apps2sd script in init.d...anyways I'm not sure what that relates too. The back of the phone did heat up quite bit...
So after I tried rooting / going back to stockrom / rooting again....nothing is working.
Everything I put on *#06# it always shows IMEI NULL / NULL no signal / baseband version Unknown / IMEI SV unknown.
It's so frustrating, I should've never done any roms. Can I still recover my phone to work? It is a Fido phone, and no I don't have a receipt to have it exchange because it was a trade I did from someone off Craigslist.
I do not have the fancy Samsung Tool Box or machine. I only have a computer that I work with and that's that. :crying:
SGHI337WRC is the proper code that I have. This Christmas sucks for me.
I think I tried almost everything I've search over the web trying to fix it. I tried the method EFS PRO but whenever I open it, it give me a warning perm-root and then when I root, it freezes and I'm not sure what it's doing.
I really hope somebody can help me out, it'll be the best Christmas gift!
PS: I would really love the instructions and step by step. I am a noob, that can follow step by step instructions.
maybe briked
u most need to have special tools to fix the kind of problems my friend
Hello,
I have this problem with my phone and i don't know how to fix it, the IMEI is Null and when i enter "*#0011#" the ServiceMode is Blank !!
I tried to use GS5_EFS_Backup but it doesn't work ! Also the phoe get hot a lot, and when i put it in charge the battery level of charge is stuck in 10% always.
My phone is rooted.
Help me Please.
Thank you
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
*Detection* said:
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
Click to expand...
Click to collapse
Thank you Detection for your answer. So where can i find another S5 EFS, and how can i restore it.
Help me Please because i tried already to take it to a repair shop but they don't know how to fix it, that's why I wanna try to repair it myself, and i think its one of the repair shops who wiped the EFS partition without making a backup (because i give to 3 repair shops and they don't know how to fix it).
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
*Detection* said:
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
Click to expand...
Click to collapse
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Nope, not if you've deleted the EFS partition - that contains the IMEI and Radios
Ok thank you, ill try to contact samsung after sales service.
Hi everybody,
I have same issue:
I needed to update SU-binaries and tapped accidentally on CWM/TWRP-Mode instead of normal. After this IMEI is null, Service Mode blank, sudden reboots and unable to install any Apps (always saying no free memory). uninstalling App causes reboot.
I have efs backup made with (PhilZ Touch) CWM, but I'm not able to fix the problem with it.
What I tried:
flashing Stock ROM + updating Bootloader in Odin
this Guide (except Samsung Tool and Terminal Emulator steps, as I can't install any App)
CWM script
I really don't know what else I can do. Does anybody have some other ideas?
Also backing up is not possible, now. EFS Professional says specified PIT file does not exist, even when I choose all partitions.
FIXED. Possible solution.
Fixed. Went to a shop to repair IMEI/EFS.
It seems there is something called "IMEI NV Generator", this should also do the magic and would have saved me some money.
samsung S5 Imei Proplem
zicozack said:
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Click to expand...
Click to collapse
I have the same problem after trying to change the original IMEI>>> any help please
Please take a look here and here.
I'm writing this post today because I recently purchased a Galaxy S6 from a shop that had its IMEI repaired without knowing it. The two major problems I experienced with the phone were due to a damaged DRK (Device Root Key) and wifi passwords not being remembered after reboots. The solution for forgotten wifi passwords turns out to be fairly simple so I will document here... This should also work on other devices that have similar issue.
Your device will need to be rooted for this procedure.
Several post throughout XDA recommend setting ro.secure.storage=false in build.prop to work around the issue, which isn't a solution. I'm not knocking whoever came up with it, but there are problems with that approach. One you will lose some of the security your device has to offer & two you will never be able to use WiFi conveniently on a straight stock ROM without root.
The problem is caused by having damaged ss_data (secure storage data) inside your devices EFS partition probably because someone messed around in there. Whether it was Samsung through an OTA or some user trying to "repair" the IMEI the fix is easy.
To repair this issue backup EFS partition with TWRP and make sure a copy resides on your PC. Then use a root file explorer to delete ss_data in /efs. Reboot, fill in wifi settings, reboot again and prosper. You may now install a stock ROM, OTA updates, etc without wifi connectivity issues on reboots.
DO NOT TOUCH ANYTHING ELSE IN EFS!!!
I found the solution here:
http://forum.gsmhosting.com/vbb/f452/i9505-no-wifi-after-unlock-1827968/
Dank!
Thanks for the guide!
I had that problem on my Note4 with MM, I restored my EFS backup (EFS, MDM1M9KEFS1-2-3-C, Modem) and I solved the problem
Luckily you had an EFS backup. ? This will work if you don't have one.
Are there any services or apps that could cause this problem if they are disabled?
I just tried deleting ss_data and my wifi passwords are still gone after reboot.
I know this is an old thread but the solution worked for my S8 SM-G950FD. Thanks a bunch!
Geofferey said:
I'm writing this post today because I recently purchased a Galaxy S6 from a shop that had its IMEI repaired without knowing it. The two major problems I experienced with the phone were due to a damaged DRK (Device Root Key) and wifi passwords not being remembered after reboots. The solution for forgotten wifi passwords turns out to be fairly simple so I will document here... This should also work on other devices that have similar issue.
Your device will need to be rooted for this procedure.
Several post throughout XDA recommend setting ro.secure.storage=false in build.prop to work around the issue, which isn't a solution. I'm not knocking whoever came up with it, but there are problems with that approach. One you will lose some of the security your device has to offer & two you will never be able to use WiFi conveniently on a straight stock ROM without root.
The problem is caused by having damaged ss_data (secure storage data) inside your devices EFS partition probably because someone messed around in there. Whether it was Samsung through an OTA or some user trying to "repair" the IMEI the fix is easy.
To repair this issue backup EFS partition with TWRP and make sure a copy resides on your PC. Then use a root file explorer to delete ss_data in /efs. Reboot, fill in wifi settings, reboot again and prosper. You may now install a stock ROM, OTA updates, etc without wifi connectivity issues on reboots.
DO NOT TOUCH ANYTHING ELSE IN EFS!!!
I found the solution here:
http://forum.gsmhosting.com/vbb/f452/i9505-no-wifi-after-unlock-1827968/
Click to expand...
Click to collapse
Your 2016's thread just gave life back to my Wifi and Bluetooth on my S6, man you are the real MVP!
Doesn't work on my Note Edge as there's no ss_data in the /efs on Kitkat.
The Story
Don't even know where to start. Okay so I have a SM-935W8 (Canadian Version) and it was working perfectly fine running Project Dream rom the S8 one. I decided to flash angelo's Pixel rom for S7 Edge and for some reason when it booted, the network had a cancel sign meaning no network. Once I finished the initial setup, calling, messaging , and data weren't working. Luckily I have a backup for EFS and RADIO in tar, img. and tar.gz formats. So I downloaded the Partitions Backup app and restored the EFS and Radio files, it said successfully restored. I rebooted my device and the issue was still there, no network. So then I installed the stock ROGERS (Provider) rom from SAM MOBILE and it came up with some DRK error and my phone would not boot. So then I quickly used ODIN to flash twrp and then flash Superman Rom (Love it) and use dm-verity bypass.zip to get past the drk error. Then I attempted many other things but to no avail such as flashing the EFS tar through ODIN which caused a "Software Error" and phone to be stuck on a light blue software error screen so I had to use smart switch to FULLY restore the phone back to booting up, then once again I flashed twrp and Superman rom with dm-verity so I atleast have root and a decent rom to work from.
The Problem and What I Have at Disposal
So essentially, I currently have a new section in settings under Connections called "SIM card manager" for managing sim cards even tho I only have 1 slot, it shows that the SIM is ROGERS and LTE/3G/2G in there, but it can't connect to a network and keeps saying Not Registered on a Network. Also, there are 2 IMEI's since my phone thinks theres 2 SIM slots but I really only have 1 slot. BUT HERE IS THE MAIN ISSUE, THE ROOT OF ALL PROBLEMS, the IMEI is reading as "000000000000000" and the IMEISV is "01". Hence im getting Not Registered on a Network. No secret codes such as *#06# are working, keeps giving the Not Registered on a Network error.
I have the EFS and RADIO backups in img, tar, and tar.gz formats as well as screenshots of all my MAC and Bluetooth addresses, IMEI and Serial #'s and all that information. So essentially I feel fully ready to solve the problem but everything I try keeps failing. My EFS restoration says successful in the APP but upon reboot, theres no change. Flashing the EFS through ODIN messes up phone harder. When I use EFS Professional Tool, where do I place the partitions so they show up in the tool?
I used this post to try to fix it: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
BUT when I'm flashing the combination through ODIN in AP, it goes to NAND write or whatever and gets stuck, sometimes it gets stuck on Analyzing files or something. I tried every single ODIN version. I really could use some expertise on this issue. A step by step written tutorial, some method anything!!!! Help on this post or even teamviewer or skype for live help would be appreciated. Please help and I'm willing to compensate for successfully helping me fix my issue..
Did you ever sort this out? I'm in a similar situation, except that it does occasionally show my IMEI but also 'baseband unknown'. But still no network access.
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
012345678 said:
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
Click to expand...
Click to collapse
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
jamesroodney said:
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
Click to expand...
Click to collapse
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
012345678 said:
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
Click to expand...
Click to collapse
Sorry, I should have clarified. I have an S7 (SM-G930W8). I only tried this thread because the issue was identical to mine and I couldn't find anything similar referencing the S7 specifically.
For anyone coming across this thread in the future, although mine was an S7 I think the issue would apply to both. I ended up ordering a z3x in order to use the patch certificate. But it wasn't that easy; the firmware had to be downgraded to marshmallow first which wouldn't work in Odin until I tried just flashing the BL and CP files first, then rebooting and flashing the AP and CSC files separately. In fact, the AP file froze the first time but passed on the second attempt. After that, everything was downgraded to android 6 and then the patch certificate option worked and my s7 connects to the network again.
I'm having a similar problem with my sm-g935w8 Rodgers but has been unlocked. A couple days ago i looked at my phone and it was showing a no signal symbol and I look for my phones information and it showed unknown in all categories, the imei say unknown, and it's not reading the sim. Help me
I am having the same problem after installing TGP ROM.
Graschuk said:
I am having the same problem after installing TGP ROM.
Click to expand...
Click to collapse
Did u Found any solution? am still in the same position as u r in.. i have also installed TGP ROM ... I Have Also Posted there my issue that i selected the latest bootloader nd modem blah blah
Wipe everything in twrp advanced and..
Flash latest stock rom for your model and it'll fix the issue
I think u need to see this
https://forum.xda-developers.com/showthread.php?p=78868375#post78868375
These two threads are the fountains of info :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
This one specifically for S7 edge, whole lots of info.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
This one for advanced users who know what they are doing.. it isn't specifically for s7 series but has a universal approach to understand concepts.. don't use the provided drk (prov data) and csc restoring files, they aren't for s7 edge.
Always backup efs and all radio/serial related info firstly after rooting. Good luck
Sent from my S7 Edge using XDA Labs
Device: Asis Zenfone Max1 Pro- ASUS_X00TD
On booting the device, I am getting the following error message " Your device is corrupted. It can't be trusted and may not work properly"( picture attached) " . The device boots if I keep on pressing the power button. From the research I did on this it seems, the software ( image ) was corrupted and I needed to install the software from the brand website. So I downloaded the image file and installed it following the recommended procedure. However the error is still persisting.
Is this error only due to a software problem or it can be a hardware related problem as well? If it is a software related problem only, how do I resolve the problem?
Thanks in advance for any help.
PS: Mods if this is not the correct forum for this question, kindly point me to the relevant forum and will post the question there. Thanks.
Problem becomes more problematic
Am bumping this up as this problem is becoming an unmitigated disaster.
Contacted ASUS customer care with the problem as detailed in OP.
Their support rep gave a solution which involved going back to a previous version of the image. Reason he gave was that the image I had flashed after d/loading from their website was a beta version and not stable.
Followed the process.
End result ? Now the device is asking for a password which feature ( password security ) I did not activate at all.
I will appreciate if someone can help me fix this mess.
TIA
aCs_ND said:
Device: Asis Zenfone Max1 Pro- ASUS_X00TD
On booting the device, I am getting the following error message " Your device is corrupted. It can't be trusted and may not work properly"( picture attached) " . The device boots if I keep on pressing the power button. From the research I did on this it seems, the software ( image ) was corrupted and I needed to install the software from the brand website. So I downloaded the image file and installed it following the recommended procedure. However the error is still persisting.
Is this error only due to a software problem or it can be a hardware related problem as well? If it is a software related problem only, how do I resolve the problem?
Thanks in advance for any help.
PS: Mods if this is not the correct forum for this question, kindly point me to the relevant forum and will post the question there. Thanks.
Click to expand...
Click to collapse
ASUS OTA updates corrupting device software & hardware both
*****Problem Solved*****
The problem not just with the software but also the hardware was caused by ASUS OTA updates.
Problem #1
The device got corrupted. Whether it was corrupted or whether it was just an erroneous error message is a matter of enquiry/research. Neither am I interested nor do I have the time to waste any further on this disaster.
Problem #2
The mic stopped working. This was remedied solely by rolling back to a prior version as advised by the customer care rep of ASUS.
Long story short which is still quite long ( apologies for being long winded )
After applying firmware rollback as advised by ASUS call center rep, the device got stuck at asking for a PIN/Password.
Given my illiteracy of technical issues, I did not have the foresight to do a simple factory data reset and move on.
So, I wrote to ASUS customer care. The incompetent people at ASUS customer care asked me to go to a different version of the firmware. That did not solve the problem. They then responded that I have to get a PAID service done to remedy the problems which would include service charges both for software and hardware issues SEPARATELY.
I gave up in disgust and decided I would purchase a new handset.
As luck would have it, Youtube referred me to a video on the issue.
Following the process shown in the video I was able to remedy the device corrupted error message.
Now I inserted a SIM card in the phone to see if it was working. It was still not working properly.
Then I googled for mic related issues. I came across links which suggested that mic functionality in these devices had been messed up by OTA updates.
So, I decided to go back to the firmware dowgrade.
I installed the downgrade firmware.
I did a factory data reset.
I activated the device.
The device is now functional.
Learnings from this disaster:
ASUS personnel are either grossly incompetent
OR
the company i.e. ASUS is running it's business in an unethical way.
Resources used to solve the problem:
Firmware applied to get the device functional
UL-ASUS_X00T-WW-16.2017.1912.060.999-user
Link: https://dlcdnets.asus.com/pub/ASUS/...272.532609309.1588748286-143972924.1567247258
Youtube video link
https://www.youtube.com/watch?v=qfFt0eKDFfU
For the moderators of the forum:
Can you kindly amend the subject of the thread to " ASUS OTA updates corrupting device software & hardware both". Thanks for your help.