Hi all
I have quite a big problem with my I9505... Factorymode is corrupted in my EFS folder, but because of KNOX, it will not let me do anything, all my root apps are now gone (Hint root explorer so I would be able to fix it)
Does anyone have a great idea to what I could try to do to my phone. It will not let me connect to ADB because it doesn't see my phone as a rooted unit
Best regards
Solved!!
I just downgradet to the earliest firmware without knox, re-rooted it, and voila... Now my phone is back up and running again
Related
Hello,
I have an S4 GT-I9500 and suddenly am having the "Not registered on network" issue. That is: I cannot receive or make phone calls and SMSs, all the rest of the phone is working OK (including Data Connection 2G/3G, which is confusing for me).
I am on stock rom Android 4.3, Baseband I9500UBUEMK1.
I think that the problem is related to the fact that a few days ago I have rooted the phone, and installed Titanium Backup to delete samsungs bloatware. However, after all deletions (I think that I have deleted only safe things), everything was working perfectly, but suddenly today I noted that I cannot receive or make phone calls.
I have read many many threads in this site, but I am still confused on what is the cause and the solution. I have checked the IMEI, and have found that the IMEI in the back of the phone is 3571****, and the IMEI reported by the phone´status is 35299****. I can´t understand what might have changed my IMEI.
I went with ES File Explorer in root mode to the beginning of the filesystem, and have found the EFS folder ... there are many folders and files in it.
I don´t have a previous backup of this EFS folder, but I have read that there are some cases that the IMEI is recovered doing some procedures...
Please help me !! I don´t have experience flashing ROMS or modems but if there is hope ...
Thank you very much.
paggps said:
Hello,
I have an S4 GT-I9500 and suddenly am having the "Not registered on network" issue. That is: I cannot receive or make phone calls and SMSs, all the rest of the phone is working OK (including Data Connection 2G/3G, which is confusing for me).
I am on stock rom Android 4.3, Baseband I9500UBUEMK1.
I think that the problem is related to the fact that a few days ago I have rooted the phone, and installed Titanium Backup to delete samsungs bloatware. However, after all deletions (I think that I have deleted only safe things), everything was working perfectly, but suddenly today I noted that I cannot receive or make phone calls.
I have read many many threads in this site, but I am still confused on what is the cause and the solution. I have checked the IMEI, and have found that the IMEI in the back of the phone is 3571****, and the IMEI reported by the phone´status is 35299****. I can´t understand what might have changed my IMEI.
I went with ES File Explorer in root mode to the beginning of the filesystem, and have found the EFS folder ... there are many folders and files in it.
I don´t have a previous backup of this EFS folder, but I have read that there are some cases that the IMEI is recovered doing some procedures...
Please help me !! I don´t have experience flashing ROMS or modems but if there is hope ...
Thank you very much.
Click to expand...
Click to collapse
Something similar happened to me some weeks ago, but my case was different because I lost my imei but it was a generic one, (started with0049..) Everything was fixed when I installed a stock firmware through odin. Go to sammobile, download any firmware suitable for your model and flash it following these instructions: http://forum.xda-developers.com/showthread.php?t=2265477
asantand said:
Something similar happened to me some weeks ago, but my case was different because I lost my imei but it was a generic one, (started with0049..) Everything was fixed when I installed a stock firmware through odin. Go to sammobile, download any firmware suitable for your model and flash it following these instructions: http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
Thank you for your answer. Do you think that is better to go flashing directly, or a factory reset should work also ?
Am I going to have any problems with the fact that the phone is now rooted, and (I think) with Knox in "non-stock" ?
Thank you.
paggps said:
Thank you for your answer. Do you think that is better to go flashing directly, or a factory reset should work also ?
Am I going to have any problems with the fact that the phone is now rooted, and (I think) with Knox in "non-stock" ?
Thank you.
Click to expand...
Click to collapse
I don't think factory reset will work, I'd flash the firmware. Flash a stock one, through Odin.
As regards knox... If you rooted the phone you might have knox warranty void 0x1, it depends on the bootloader. When you enter in download mode you will find out. If you still have knox0x0 or nothing displayed it means that warranty void was not triggered. Anyway flash the same firmware that you have now. You can find it in sammobile web page. Hope it works!!!!!
Well, finally I went with the phone to a repair technician who fixed the IMEI problem using a Octopus Box.
The reason the IMEI was altered is still unknown.
Alright so... I got this N900T and rooted it and tripped the knox warrenty bit.
I installed the latest DomPop and read how the efs partrition had some issues and it being easily borked, and well I didn't wanna risk it. Rather than look into how to back it up properly using better tools, I had remembered a command from the S3, su reboot nvbackup, which is supposed to back up the efs stuff to a safe place on the phone. However, upon finishing that command it bootlooped. Well, i then ODINed back to 5.0. my baseband version is unknown, IMEI is unknown, all of the typical EFS is messed up stuff. So i tried, stupidly, the other command to restore the backup, su reboot nvrestore, and upon running that command it forced itself in download mode unable to boot.
i odined back to the 5.0 firmware about 4 more times and nothing happened.
I searched and searched and i tried following http://forum.xda-developers.com/showthread.php?t=2567133, i tried the the script it links to remake the partrition for the EFS.
My serial is still on the phone, i skipped down to the part about repairing the imei. I put my phone in RMNET+DM+MODEM, however it doesnt get picked up by EFS Professionals NV Tools. Any more ideas or help?
Also, is it safe to flash the 4.4 Kitkat without the phone bricking?
If there is anything i cannot do on my computer, are there services cheapish i can send them to and have them flash my IMEI back onto my phone?
Thanks in advance!
Me can not follow
Okay, so I used "reboot nv backup" without first researching to to back up my EFS partitions. Upon reading further into the stuff, I have found that that method destroys your partitions and shouldn't be used. I then, kind of freaking out used the other function "reboot nv restore" which is supposed to restore the backup, but instead it caused my phone to not be able to boot. So I odined back to stock 5.0. I have tried flashing just the modem, I have tried downgrading to NK3(4.4) but that had not helped me either. My baseband is still unknown and my IMEI is still null.
Is the only way to fix this with a UART cable and box? Are there any paid services I can use online to repair those partitions? I attempted to use EFS Professional, however it couldn't talk to my phone, either the SPC Code or the 16 digit security code wouldn't work so I couldn't write the IMEI back that way.
Ravenjolly said:
Alright so... I got this N900T and rooted it and tripped the knox warrenty bit.
http://forum.xda-developers.com/showthread.php?p=46436273
Not sure how is this going to help but there was a user (other than the poster) managed to recover his imei. I believe you could use any help at this moment.
Click to expand...
Click to collapse
Rosli59564 said:
http://forum.xda-developers.com/showthread.php?p=46436273
Not sure how is this going to help but there was a user (other than the poster) managed to recover his imei. I believe you could use any help at this moment.
Click to expand...
Click to collapse
Sorry, I have tried this and it didn't work. Thank you for looking for me.
Have seen many people with IMEI unknown and none of the threads I have read managed to get it back. As far as I know you are now hard bricked, at least regarding the actual phone part of your phone.
Dear esteemed experts,
I’m hoping you can assist in my hour of need: My partner has a stock unrooted European G900F S5, which unfortunately had a massive software glitch causing it to crash on start up. Long story short we managed to get to the factory reset options and do a full reset, which cured the problem, however my partner’s data has now been lost.
She regularly backed up and had all the autobackups enabled so contacts, sms, mms, pics, videos, settings, etc were all restored with relative ease, but it appears the most valuable thing to her, her WhatsApp conversation backups were stored by Whatsapp on the internal memory rather than the SD card (brilliant piece of software design going on there) so they are gone. Smart Switch restored all of the other WhatsApp data on the internal memory as part of its “data” backup but not the backup files…
I’d like to run a data recovery program to see if they can be recovered, but am hitting dead ends at every turn: none of the specialist android recovery programs (such as dr fone) appear to work on a lollipop S5 unless it is rooted; none of the usual PC recovery suites can work on MTP or PTP modes and a mass storage connection is no longer possible (at least without root); and the only way to permanently root is to downgrade the stock rom (which will likely overwrite the data I am trying to recover) and use something like towel root on KitKat. In any event, she’s very happy with an unrooted phone with OTA updates and so wouldn’t wish to end up with a rooted phone anyway, so I’d have no real interest in a custom bootloader install, etc: I just want temporary access for dr fone!
To that end, I wondered if there was by any chance a crafty way of obtaining a temporary root in lollipop (a re-root after restart is absolutely fine by me) just so I can run a recovery program and see if we get any luck? If it came to it I think she’d be prepared to sacrifice a knox trip if she got her conversations back….
Apologies if this has been asked before, but I could only fish out advice on permanent rooting for s5 in my searches (both here and on google).
Many thanks for your assistance!
Dav
No way to root lollipop without tripping KNOX if you are not willing to downgrade to KitKat first, which would defeat the object as you could root with towelroot then anyway
Only way to root Lollipop is to flash CF Auto Root with ODIN, which WILL trip KNOX, and it is permanent unless you choose to unroot / flash stock again
This is the file you need to flash with ODIN (Extract and add it to the AP or PDA section of ODIN with the phone in download mode)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
PS: Questions go here
http://forum.xda-developers.com/galaxy-s5/help
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.
Hi all, as the title says, my efs folder is inaccessible. Firstly let me explain. I bought a phone, it had the Paul pizz rom in it and I didn't like it. So I flashed the resurrection remix rom. It didn't have all the bells n whistles I wanted, so I tried the official res remix rom. Somehow I ended up with an efs problem. I ended up with an efs invalid argument error and from what I read, I did the whole adb efs fix. The error was gone. I ended up flashing a repair firmware back to bog5 and started from scratch. I worked my way back up to installing the modest rom and it works 99% flawlessly and I am happy enough to keep it. Here is the catch, I used kingo root and have ended up with a bad keyboard lag that's driving me nuts. It is unknown to me if the kingoroot caused the efs corruption or if it was just a bad flash going from one rom to another. I have tried several root browsers, made sure they all had root privileges, and no matter what, I can NOT get access to what's hidden in my efs folder. They always say it's empty. Now, here is the kicker, I got another note 4 for my son. Downgraded from 6.01 to 5.01 bog5, then up to 5.11 and flashed the modest rom on his. Instantly his phone has access to the efs folder. My note 4 works, can make calls, text etc. Imei is shown in settings, all info shows in settings as normal except one thing, on my phone it says configuration version not available whereas on my sons phone it gives a configuration version. I just can't figure out how to gain access to the efs folder to try to fix this extremely annoying lag. I DID make a complete backup of my system from when it had the Paul pizz rom, so the efs partitions should be intact there but I don't know if that would help or even where to start. Can someone please help?
Well, I just fixed my phone and thought I would share what happened. It seems that the guy that loaded the paulpizz rom on the phone before I bought it used a different version of twrp. He used a version for n910f, whereas when I began my rom search, I used one for a n910v because thats what the phone is. I was having a hard time with it so I reverted to stock, rooted, installed verizon twrp, and bam! No efs access. The difference in recovery programs is what screwed me up in the first place. I figured it out when I tried to restore his rom backup I made. The efs files were not working when it restored. I remembered what version of rom it was, and tried a twrp for 910f, and voila! So, now I have all functions working as blazing speeds, can actually access the efs folder, and no more damned lag! Big thumbs up button to me!