Related
just rooted my evo3d, everything went great and i even git CWM to install the first time correctly. heres where i think i went wrong-
i downloaded rom manager and i attempted to use it and it worked great. to me it seemed like it worked because i was able to choose my phone and even flashed the CWM over the original one i had. i made a backup of my stock rom and tried a rom from the dev forum, didnt like it and tried to switch back and got the MD5 mismatch error when i tried to restore my stock rom. now, i thought i would try to flash the original CWM which was blue over the CWM(orange) and then attempted to get the rom to restore. that was also a fail. what can i do? i read that installing busy box could effect this? any help would be appreciated.
sucks but it happens download the RUU from here and reroot if you need too
FIXING MD5 MISMATCH
adb shell
# cd /sdcard/clockworkmod/backup/name_of_backup
# rm nandroid.md5
# md5sum *img > nandroid.md5
gaaah i dont have ADB installed on my mac. is there not a simpler way? anyway to fix this?! i dont think i need to reroot honestly..
Nope sorry.
I may have found a way to fix the MD5 issue.
Well, it worked for mine.
I saved a backup of the stock ROM before I installed the needle kernel.
it was named 2011-08-01-23.53.47
The I saved another backup of the ROM with the needle kernel/
it was named 2011-08-02-19.06.28 w/ needlekernel
What happened was that on the sd card the backup folder was named 2011-08-02-19.06.28 w/ then inside that folder was another folder named needlekernel . And that folder contained the backup files.
It seems that putting the space in the name caused it to create another folder within the backup folder instead of just having the backup files in there. I kept getting the MD5 mismatch when I tried to restore that backup.
So I took the files out of the needlekernel folder and put them in the 2011-08-02-19.06.28 w/ folder. I then deleted the needlekernel folder. The last thing was to take the (space)w/ off of the end of the folder name so it was just as the program named it to begin with.. 2011-08-02-19.06.28
After doing that I was able to restore the backup through ROM Manager. So apparently it's best not to add anything to the backup name when saving it.
One other thing I'll mention. When I restored the backup with the needle kernel in it it put the stock kernel back in the ROM.
Hope this helps anyone with the MD5 issue.
My s3 stopped recognizing the Sim yesterday, so i searched for a solution. i read in xda that its the EFS partition. I got no IMEI and no Baseband. Somehow i found 2 files on the internal SD Card: "efsbackup.tar" and "efsdev-mmcblk0p3.img".
I read this thread, but it didnt help me.
Any idea how i could fix it?
Btw, Android Revolution HD 11.0 with stock kernel
I'm guessing your Rom auto backs up the efs, so best to ask on their thread about reinstalling it
Restore your EFS backup .
jje
im going to install now arhd 11.3 and then do the restore of the efs backup.
i noticed that the backup was built yesterday evening, when the problem already was. well it seems like i got no backup, when it was working
I followed in this thread this post:
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Click to expand...
Click to collapse
and now i got an IMEI, but its still not mine: 004999010640000 / 01
If you have an efs.tar file why dont you put it in PDA in Odin?.
wont work.
deleted
Ok....then I dont understand why it backs up as a tar file then
yesterday i flashed siyah kernel, siyah probably made a efs backup. but that backup was already after that problem happened.
well i got now the 0049 imei
So you dont have a back up of you original IMEI is that what your saying?.Flashing ROMs normally is what makes a backup not flashing a kernel so Id say the backup is original.
Read this
http://forum.xda-developers.com/showthread.php?p=30682712
i read this but i dont know what to do with it. i understand that this are options to backup the efs partitions but not how to restore it how to restore it if already lost
x Schieby said:
i read this but i dont know what to do with it. i understand that this are options to backup the efs partitions but not how to restore it how to restore it if already lost
Click to expand...
Click to collapse
you need to read better then
You'll need to perform an "IMEI injection" which is a kludgy last-resort restore method that manually writes the IMEI to NVRAM; the link I provided in Part C of "Backup" will tell you how to do it.
x Schieby said:
My s3 stopped recognizing the Sim yesterday, so i searched for a solution. i read in xda that its the EFS partition. I got no IMEI and no Baseband. Somehow i found 2 files on the internal SD Card: "efsbackup.tar" and "efsdev-mmcblk0p3.img".
I read this thread, but it didnt help me.
Any idea how i could fix it?
Click to expand...
Click to collapse
That's what the efs backup is for xD
Calm down, or you'll make things worse. Unzip the efs.tar to /efs and reboot your phone (DON'T PULL THE BATTERY)
Everything should work like a charm again
Hope I could help!
LG familyguy59/Beatsleigher
slaphead20 said:
you need to read better then
You'll need to perform an "IMEI injection" which is a kludgy last-resort restore method that manually writes the IMEI to NVRAM; the link I provided in Part C of "Backup" will tell you how to do it.
Click to expand...
Click to collapse
sorry, but i still dont get it with the qpst. thats the part c you are thinking of right?
familyguy59 said:
That's what the efs backup is for xD
Calm down, or you'll make things worse. Unzip the efs.tar to /efs and reboot your phone (DON'T PULL THE BATTERY)
Everything should work like a charm again
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
going to try this now
familyguy59 said:
That's what the efs backup is for xD
Calm down, or you'll make things worse. Unzip the efs.tar to /efs and reboot your phone (DON'T PULL THE BATTERY)
Everything should work like a charm again
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
well, thats how my phone ended. i did that yesterday and my phone finally didnt even booted.
then i went to my carriers shop and told them it wont boot, and today i got a brand new phone
anyway thanks to all help!
Problem solved!
**********************
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
**********************
Original question
Hello devs,
I have Siyah kernel which auto backup my EFS, i have backup named "efs_28Aug2013-1852.tar.gz"
I want to restore from this backup because I lost my IMEI when I flashed UltimaROM
I renamed it to "efsbackup.tar.gz" and put it in the root of the sdcard
then I started adb shell & run the code
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/ efsbackup.tar.gz -C /
I granted ADB shell root access
then i went to recovery and run the command (because I can't run umount /efs while device's running it gives resource busy message)
However when I run the first command "su" in gives me this message
Code:
/sbin/sh: su: not found
so I skipped to the next command
but I get the message
Code:
umount: can't umount /efs: Invalid argument
Please guys any help appreciated
Click to expand...
Click to collapse
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
.
I've backup my efs with adb but how do you have a file on tar format, i've got a file on .img, it's normal ?
There's about nine different ways to backup the efs, .img is fine but a little on the large side at 20mb. A .tar of the same is only 5mb.
rootSU said:
Unzip it with a file manager and use a root explorer to replace manually
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for your reply, I did as you said but this only changed my IMEI from "Unknown" to the generic IMEI "004999..."
Is there something wrong in the method or my backup may be corrupt
Sent from my Nexus 7 using Tapatalk 2
Read the imei / efs thread in general.
Sent from my GT-I9300 using Tapatalk 4
Thank you again, I read the thread in the past but it looks like it has been updated recently.
I think my problem happened because a flashed a ROM with MG4 baseband, and then flashed UltimaROM with another baseband which caused my baneband to corrupt.
I tried to flash Stock ROM and install different baseband but non of this worked.
finally I flashed BTU stock ROM (Which comes with MG4) but the problem still here.
Then I installed root, deleted the efs folder and replaced all the files with the files in the backup - restart and everything is working! my IMEI returned to normal.
Thank you RootSU for your help.
hey bro,
i am stuck
help me out
- my efs(folder) is blank
- i installed stock with pit file but no help!
- right now my cell is in bootloop!
- it goes to recovery, download mode.
i have efs.tar.gz file and a folder named efs in my ext sd
how do i copy that to int memory?
can't even create a cwm flashable zip file of the same?????
help me bro.....
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
boomboomer said:
You are posting in a thread that tells you how to restore an efs backup, how much more could you possibly need?
Go to recovery, factory reset.
Get the phone to boot, unpack the .tar file and follow the instructions in the OP.
Click to expand...
Click to collapse
Dear boomboomer,
i am sorry, but my phone is in "bootloop" how am i suppose to delete the "EFS" ? that s what i am asking!!!!!
i have both efs.tar.gz and extracted folder ready in my ext-sd......
i wonder if somebody can help me with creating a cwm.zip from the .tar file
thanks ....
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
i already did so
almousawi said:
try to install stock again via odin but this time install a diffrent version (for example if you installed INU this time try INS).. before that factory reset your phone and wipe cache via recovery mode.. don't lose your efs backup it's very important copy it to your PC in case something wrong happens
Click to expand...
Click to collapse
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
hello
mikks said:
bro, thanks for your help recently i tried cm 10 also but nothing happened.
believe me i tried everything now the only option is left that is
to restore efs backup from efs.tar.gz (which is about 12 MB)
OR
create a cwm flashable zip from the efs folder which is about 22 MB)
OR
take my phone to download mode and try to push whole "efs" folder to the location with help of "ADB"
Click to expand...
Click to collapse
hello nobody is here to help......??????
mikks said:
hello nobody is here to help......??????
Click to expand...
Click to collapse
Correct this is not a paid for service .
Suggest you take it to a service centre .
know that i did that already....
JJEgan said:
Correct this is not a paid for service .
Suggest you take it to a service centre .
Click to expand...
Click to collapse
thanks for the reply, respect to your reply and interest no disrespect ...
i took that to the center but they failed and by the way they come to me in some cases... so they give me free service...
my phone is in boot loop, i have efs.tar.... can i use phills recovery ????? or can i use someone elses backup... just to boot up my device ...then i'll be good .... i just need to get my device booted up.....
Bought and activated used phone 2 weeks ago. Phone worked fine thru Friday night. Woke up Saturday to find I could not connect to cell network. Call to carrier revealed my IMEI number does not match the number they have. Somehow my phone IMEI changed to 350000000000006. Internet search revealed many others with same problem. The main difference between their situations and mine is the fact that in almost all of their cases their phone was rooted and they flashed many different ROMS to their phones and something obviously went wrong. My phone is NOT rooted and I have not tried to modify anything. Simple as that. Went to bed working, woke up broken.
I have now researched this the last few days and have no clear answer. Is it possible to set my IMEI back to my correct, legal,clean and not blacklisted value? Any help is greatly appreciated.
My guess is without a backup of the original, you can't do anything about it. Best bet is probably return it to the store you got it from and get a refund/exchange.
Edit:
Fastest and safest bet would be refund/exchange.
Little research has shown other people had a similar issue. Check Nox to make sure the phone hasn't been rooted before, if it has, you know what happened. If it hasn't, chances are the phone was flagged as lost/stolen after being sold (if 2nd hand).
As for a fix, I found this:
http://forum.gsmhosting.com/vbb/f898/g925f-imei-350000000000006-a-2044425/
Recover corrupt IMEI (without prior EFS backup folder)
Items needed
Root Explorer
Efs folder (no need to have a backup of this prior to the disappearance of IMEI folder, but it has to be this folder on the phone)
Obviously having a rooted phone
Instructions
1- With the Root Explorer to back efs folder to the SD Card
2- For safety make a second copy of the folder to the PC
3- Once both copies made to proceed to erase the original EFS folder on your phone
4 Restart the phone
5- When you start the phone, it will automatically create a new folder EFS, Root Explorer to delete the files and nv_data.bin.md5 nv_data.bin found inside the new EFS folder.
6 Copy the folder from the SAI IMEI folder we saved on the SD card and stick it on the new EFS folder created in the root directory of your phone
7- Since the SAI folder we saved on the SD card .nv_data file copy, paste into the new folder EFS generated in the root directory and rename it nv_data.bin phone, then recopy again .nv_data file rename it nv_data.bin.bak
8- With Root Explorer /efs/nv_data.bin change the owner
9. Restart the phone
If all went well you should have recovered the IMEI can check if recovered by entering * # 06 # on the phone dialer.
Thanks for the response ProdigyThirteen.
The Knox is clean 0x0. Everything I have found says the original IMEI is clean and not flagged.
I will definitely look into the procedure you provided. It looks promising. I'll take any sign of hope I can get.
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Copy the nv_data file from the SD card to the newly generated EFS folder on the phone and name it nv_data.bin. Then make another copy in the same EFS folder and name it nv_data.bin.bak.
Then you need to set the permissions for EFS folder/nv_data.bin file. They need to be set to rw-r-r. However for this procedure you need to be rooted.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Could you tell me did it work?
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Shaggydoo said:
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Click to expand...
Click to collapse
Have you tried flashing the stock firmware again? Either by smart switch or odin?
Will try again tonight when I get home.
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Shaggydoo said:
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Click to expand...
Click to collapse
I remember I did have the exact DRK error on my s6 edge one and dm verity fail. The way I fixed it was by flashing stock firmware through Odin. Quote me when you try again and I'll do my best to help mate.
IMEI
If you want to get back your IMEI try Dashboard .
you will find all your devices there, then try to find a way to write your IMEI in your phone (may need root)
Dashboard (https://myaccount.google.com/dashboard?hl=en)
Currently I had damage a new phone in the process of transferring a twrp backup from my gold note 8 onto my black note 8, but now silly of me I didn't realize I tried restoring the efs partition as well causing me to have a bad partition. Now, I currently manage to fix the efs partition and solve some issues im just stuck in trying to find the file in which I can alter the IMEI as currently its 00000000000 i've checked NV_data, but I cant seem to find the offset that contains it i've tried searching it on my working phone to see if I can spot the imei so I can find the right offset, but no dice.
edit: I've solved my problem i'm not sure if it'll work for you, but what I did was root my device, delete the efs folder which eventually game "000000000" imei and the baseband wasn't appearing as unknown anymore, then within the new efs folder that was created on its own there was a folder called efsec in which it contained !svc and svc files, so I extracted these files and edit these files with notepad++ which within there was an option for imei and it showed me all 0000000 so I imputed the original imei, and finally after a reboot I reflashed stock and then flashed a combination file which when it booted up it automatically restored my imei
THORMUNZ said:
Currently I had damage a new phone in the process of transferring a twrp backup from my gold note 8 onto my black note 8, but now silly of me I didn't realize I tried restoring the efs partition as well causing me to have a bad partition. Now, I currently manage to fix the efs partition and solve some issues im just stuck in trying to find the file in which I can alter the IMEI as currently its 00000000000 i've checked NV_data, but I cant seem to find the offset that contains it i've tried searching it on my working phone to see if I can spot the imei so I can find the right offset, but no dice.
edit: I've solved my problem i'm not sure if it'll work for you, but what I did was root my device, delete the efs folder which eventually game "000000000" imei and the baseband wasn't appearing as unknown anymore, then within the new efs folder that was created on its own there was a folder called efsec in which it contained !svc and svc files, so I extracted these files and edit these files with notepad++ which within there was an option for imei and it showed me all 0000000 so I imputed the original imei, and finally after a reboot I reflashed stock and then flashed a combination file which when it booted up it automatically restored my imei
Click to expand...
Click to collapse
Thanks for the answer. I would like to clarify one point ...
I realized that you replaced the parameter "deviceID": "00000000000" in SVC and !SVC files (in the newly created /efs/ sec_efs folder) with your original IMEI.
But what does "and then flashed a combination file" mean?
With which software did you flashed the modified SVC and !SVC files?
Maybe you just replaced SVC and !SVC files with 00000000000 IMEI onto SVC and !SVC with your original IMEI via RootExplorer for ex.?