Related
Hi all mates!
I have a problem with my i9000... I explain my problem fast:
I have extracted the BML3 and STL3 of my phone to 2 files .img... I have duplicated this files to a backup and I modified it. Now, I can´t load the original bml3.img and stl3.img because the /dev/block/stl3 doesn´t exists... not are mounted... also when I restart my phone, the /efs/ directory is empty, and the phone dont ask me for the pin... (obviously, I don´t have call service) but, If I copy the nv_data.bin to /EFS directory, the phone ask me for the pin and I can make and receive calls...
Do you have some idea to load the original stl3 & bml3 files in the phone????
-------------------
well, now I have put the bml3 and I reboot, all is ok, but when I try to put the stl3 and I obtain this message:
dd if=/sdcard/stl3.img of=/dev/block/stl3
/dev/block/stl3: cannot open for write: Invalid argument
but the stl3 partition exist! and I rooted the phone
ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl11
/dev/block/stl12
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9
all is done!!!
I had to reflash the phone after recover the bml3... Now all is OK but my IMEI... it has the famous 004999010640000 number but that is other history
awia said:
all is done!!!
I had to reflash the phone after recover the bml3... Now all is OK but my IMEI... it has the famous 004999010640000 number but that is other history
Click to expand...
Click to collapse
Simply make a Call from your Phone: +49 9901 0640000 xD
Aery said:
Simply make a Call from your Phone: +49 9901 0640000 xD
Click to expand...
Click to collapse
xDDDDDDDDD
Why in the Gods name you messed around EFS in that way?
If your IMEI is messed up, I recon so is your WIFI MAC and BT address too.
Richthofen said:
Why in the Gods name you messed around EFS in that way?
Click to expand...
Click to collapse
because I looking for restore my original IMEI number
the WIFI MAC and BT also are changed?? I don´t have any problem with the wifi... but I don´t tested the BT...
I don´t have the MAC of wifi and BT ............
but wifi works good....... at the moment!
surprise!
when I recovered the product code and I restarted the phone, it shows me the WIFI MAC !!!!
but the KIES reg continues showing me the XXXXXXXXXXXXXX product code...
awia said:
surprise!
when I recovered the product code and I restarted the phone, it shows me the WIFI MAC !!!!
but the KIES reg continues showing me the XXXXXXXXXXXXXX product code...
Click to expand...
Click to collapse
Do you try to copy the files nv_data.bin and nv_data.bin.md5 into /efs and then remove the battery without turning off the phone?
quiron said:
Do you try to copy the files nv_data.bin and nv_data.bin.md5 into /efs and then remove the battery without turning off the phone?
Click to expand...
Click to collapse
no........ I try it now
awia said:
no........ I try it now
Click to expand...
Click to collapse
any news about that?
quiron said:
any news about that?
Click to expand...
Click to collapse
The same result
i had a similar issue with my nv_data files. i backed them up to my computer, then copied a set of nv_data files over from my gf's phone, and it gave the same issue. when i copied my original ones back, it still wouldn't work. seems the signature of the file is changed, and the phone doesn't accept it. your phone has a set of backup nv_data files on the phone in the efs partition. delete your bad nv_data files, shut off your phone, and turn it back on. the phone should recognize the files are gone, and use the backup files......worked for me
edit: just to clarify, only delete the .bin and .md5 files, not the .bak files.
leave: nv_data.bak & nv_data.bak.md5
Hello,
I'm having the same problem but only have the bml3.bak and the nv_data.bak and nv_data.bak.md5.
I updated the firmware to JPH and make the changes to restore the product code to KOR from XEC the original for my country and operator.
The bml3 was corrupted and in the next reboot the phone didn't ask for the pin code of my SIM card.
I try to restore the original files, but the efs is empty or write protected, with root explorer a mount to r/w and only if I connected by usb the phone ask for the pin, and I can access to phone network and can make calls a recive it but the IMEI is the tipical 004999010640000.
The stl3 is imposible to read or write from it. The nv_data.bin can not be reinstalled because pin is not recognise and in a reboot the files are restore to previous state.
I think the nv_data are store somewhere and when the file system is mounted as r/w the efs directory is recovery from there.
Efs directory only has and .android directory, and nv_data.bin, nv_data.bin.md5, .nv_state. No imei directory, etc
awia you has some good news, i'm from spain to, it's possible to speak somewhere in spanish.
Do you recomend to take the phone to SAT?
I bought it in the Telefonica FlagShip Shop in Madrid.
Hello,
An update over my previous comments.
If I used rootexplorer to paste .nv_data.bak and .nv_data.bak.md5 that I backup before and then go to efs directory and mount r/w and immediately copy the previous pasted files, then the process start and ask for my pin, and then the imei is restored. The problem is that this is temporal and only works in the current session, if you reboot the phone then you must to make the same steps. I don't know if I can make a sh to do this step more automatically, because I don't know how and what rootexplorer remount in r/w permissions, may be someone can help me in this tasks.
In my previous comment I said that the pin prompt only has shown if the phone is usb plug in but this is not true, works in all conditions.
About the process, I suppose the bml3 contains all the information and in the bootload process this bml3 set the stl3 and mount over efs directory but for some reason this is not working with my phone because the changes over the bml3, I don't know how can I reestablished it. I use the redbend_ua for that and the bml3 are now like my backed-up one, but still doesn't work.
Hi, i've just dialled *#06# to get my IMEI and my imei number has changed from 352*********** to 00004**********.
Does anyone currently know of a way to change the imei number back? Thanks in advance.
Your Friend
Phil
I noticed on JM6 and JMA that it made my IMEI number incorrect as well, so when I entered it, it didn't recognise it to change the CSC.
Not sure if there is a way, hopefully so!
I'm sticking with JJ7 now on my replacement tab until we get a proper recovery mode in place.
I had this on my galaxy S. Solved it by backing up the efs directory to be safe. you need root. then delete everything in the efs dir except nv_data.bak then rename it to nv_data.bin and reboot. It should rebuild the efs dir correctly and put the imei back.
But this only works if the nv_data.bak file has not been modified in anyway otherwise it will rebuild with the 0044 imei.
Lordao
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
diigibio said:
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
Click to expand...
Click to collapse
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
zerocool76 said:
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
Click to expand...
Click to collapse
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
rgbc said:
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
Click to expand...
Click to collapse
I destroyed my original nv_data.bin editing with a txt editor instead hex editor, plus I deleted baks files for mistake with root manager (no booze when playing with this **** anymore ), I didn't know that the IMEI is encrypted in that file. When I found a copy in my sdk (that I didn't make!?) I restore everything, and after that time I flashed a lots of Firmwares and Modems, but my imei is still ok.I know that a Galaxy S firmware made this issue because it was changing the nv_data and it didn't match anymore with the phone, so corrupted IMEI.I'm wondering if there is a firmware that is doing the same with the Tab
Mine has done the same but with JK5. First noticed when I did the Samsung UK offer thing. Completely different IMEI to whats on the back of my Tab.
Sent from my GT-P1000 using XDA App
Sorry to dig up and old thread, but is this still an issue, can say flashing back and forward from Overcome for example corrupt IMEI etc?
Interesting - are other Samsung devices able to have their IMEI changed?
What this means is that to a technically capable enough thief (or one who knows someone technical enough that will work on credit), Samsung devices are much more valuable: Normally if your mobile got stolen and you had the IMEI, you would report it to your network and they would have it blocked on all networks. Furthermore the police would use the IMEI to prove that the device is yours if it were recovered. If the IMEI can be changed, the device can't be identified and can't be blocked from networks. It only needs slight tweaking to make it appear valid. Don't know about the implications for post-registration call routing, but the thief wouldn't care about that.
In the US, gsm carriers won't block the number - they seem to view stolen phones as a potential new subscriber.
hello,
i have the same trouble ( imei change)on galaxy tab , but the phone work normally (for now ...).
Can i let it so , or could have trouble in future?
because i don't save nv data folder, and i'm not very good to restore rom.The mod was made from my friend.
excuse for my english ,bye
zerocool76 said:
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Click to expand...
Click to collapse
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
paul.robo said:
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
Click to expand...
Click to collapse
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
ktmman said:
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
Click to expand...
Click to collapse
So i got my IMEI no.back but i still don't have a data connection. The strange thing is if i swap sim cards
with my phone it works so im not sure whats wrong with it.
help pls,
i have been wrongly delete the .nv_data.bak.md5 & .nv_data.bak file in efs folder without any backup done.
but i still have the file nv_data.bin.md5 & nv_data.bin in efs folder,
and i been Flash from DXJPA , to JPY , to JPU, to JVB , to JVE , to JV5.
what can i do to get back the .nv_data.bak.md5 & .nv_data.bak file in efs folder??
or can i just get the file from another phone and do some editing ??
y not 1 answer to me ?
can i just get the file from another phone??
just copy and paste it on my phone ??
what will happen if i do by this way ?
Ofc you can try.Here are the files. http://hotfile.com/dl/120562433/d70ac90/files.zip.html
thanks ,
This file is either removed due to copyright claim or is deleted by the uploader.
i have few friend use SGS phone, i can simple get the file from them ,
the problem is i don't know when will happen if i just copy the file from other SGS phone and paste it on my phone .
the imel number will changes to my friend imel number ?
I dont think your imei changes, but your product code might change. Imei is in "imei" folder.
Ps: Hotfile sucks I uploaded files by myself....
They're the backup files and it won't cause a problem that they're deleted. They should be recreated by rebooting your phone if not, just copy the original files and rename them.
You should definitely disregard previous advice in this thread.
I have a i9070 and I'm trying to backup my EFS folder, but I can't find all the important files like nv_data.bak in there.
I have rooted my phone and installed Root Browser. I browse to my EFS folder, I copy it and paste it somewhere else. I've checked the option to show hidden files both in the cell phone and in my computer, but when I browse either that folder or its copy I only get these contents:
/bluetooth
cryptprop_lock_pattern_tactile_feedback_enabled
cryptprop_lockscreen.password_type
cryptprop_persist.sys.timezone
/dmp
GUARDFIL
nv.log
/wifi
cryptprop_applied_result
cryptprop_lock_pattern_visible_pattern
cryptprop_lockscreen.patterneverchosen cryptprop_rebootMode
essiv
/imei
/RFHAL
cryptprop_lock_pattern_autolock
cryptprop_lockscreen.lockoutattemptdeadline
cryptprop_onetimeboot
cryptprop_securewipedata
/FactoryApp
nv_data.bin.md5
/RFHAL.DEF
Note that there's this file called "nv_data.bin.md5", but it's empty.
Any clues about why the "super important files to back up" are missing and how can I make sure that I have a copy of them?
I know that a lot has been asked and answered about EFS in this forum and I've searched for this specific issue, but I couldn't find anything that would help me.
Thanks!
persio said:
I have a i9070 and I'm trying to backup my EFS folder, but I can't find all the important files like nv_data.bak in there.
I have rooted my phone and installed Root Browser. I browse to my EFS folder, I copy it and paste it somewhere else. I've checked the option to show hidden files both in the cell phone and in my computer, but when I browse either that folder or its copy I only get these contents:
/bluetooth
cryptprop_lock_pattern_tactile_feedback_enabled
cryptprop_lockscreen.password_type
cryptprop_persist.sys.timezone
/dmp
GUARDFIL
nv.log
/wifi
cryptprop_applied_result
cryptprop_lock_pattern_visible_pattern
cryptprop_lockscreen.patterneverchosen cryptprop_rebootMode
essiv
/imei
/RFHAL
cryptprop_lock_pattern_autolock
cryptprop_lockscreen.lockoutattemptdeadline
cryptprop_onetimeboot
cryptprop_securewipedata
/FactoryApp
nv_data.bin.md5
/RFHAL.DEF
Note that there's this file called "nv_data.bin.md5", but it's empty.
Any clues about why the "super important files to back up" are missing and how can I make sure that I have a copy of them?
I know that a lot has been asked and answered about EFS in this forum and I've searched for this specific issue, but I couldn't find anything that would help me.
Thanks!
Click to expand...
Click to collapse
You do not backup it like that, need to backup partition. Look, there was some guide in CM10.1 thread from Frapeti I think.
Hi !
I am goint to coment about my problem.
I have a backup of the folder EFS, but it isnt a full backup, because o dont have the hidden files, which starts with a "."
When i was flashing my phone, ocurred an error, and appeared a black screen with red letters that said "rst_stat 0x0000000000000"
Well, the phone goes well, i have 3g, but i cant do or receive any call, y cant send o receive messages.
I realise that i dont have the files .nv_data.bak and .nv_data.bak.md5
I think this is the reason why I can not use the cell
If i delete the folder EFS, that files dont reappear.
What can i do?
can someone send me these files for private or mail , I really need some help. please.
Thanks to all.
Regards.
In S3 mini is IMEI probably stored in CSPSA partition, in EFS folder aren't nv_data files.
and, what can i do ?
Please, help me