Related
I played with the OEMName reg settings as posted here to tinker with the other oem apps, and it stopped all my applications from working, I had to hard reset to get any apps to function again. Luckily, I had saved my 7008 backup files and I used the method posted [url="http://forum.xda-developers.com/showthread.php?t=1060103&highlight=backup+file+locations+zune]here[/url] to revert my locked 7392 Focus to the 7008 backup. I had saved the backup. These are some observations:
- When I updated to 7390 and created the backup, my phone was already unlocked and prevent unlock was done, when I restored my backup, the unlock was preserved
- the unlock retained through my subsequent update to 7392 (expected, but nice to know)
- The sideloaded apps on the phone at the time of the 7008 backup also installed with the backup
Even with my phone on the pin lock, as soon as I connected it to the PC, Zune opened and synced and prompted for the update. Is this new bahavior?
I was able move the saved backup files into the Windows Phone Update folder after the phone was connected and synced.
Once I was back to 7008, I hard reset the phone and updated again without setting up my Live Account info to create a "pure" 7008 backup for the purpose of posting here for others to tinker with.
If there is interest, i will post the files when I get home.
That backup could be very handy to have around! Please post it!
Backup is for one phone only, not all around. I know, you can change the DeviceId, but it will fail when you try to restore to another phone. I guess a backup is useless for others.
The best backup is the firmware itself.
I do believe this will work. There are two .xml files in the restore point. Each of these has a deviceID field. I believe that if you change these fields to your own unique device id number and wait until after the phone is connected to zune to replace the files, you may be able to use someone else's backup files on your phone.
Also, I reverted my phone to 7008, but once there, I was unable to get the chevron unlock to work. I'm not sure why this is or what I did wrong.
Later tonight, I will try to restore my wife's phone using my restore point as a proof of concept
Proof of Concept failed...
this is what I did...
1. First, I located the existing backup files on my computer.
C:\Users\#USER#\AppData\Local\Microsoft\Windows Phone Update
In this location, there is a folder with a long name that looks like this:
B12da62f - d8d2d122 – 81d60512 - 6aaa3f12
This folder holds your restore files. This number is your unique device ID number.
2. I copied this folder and its contents to a safe place in case I needed it later. I have made it a practice to make a backup copy of all my backups so I can restore to any point. Restoring your own backups definitely works. I’ve done this several times with many old and new backups. See this thread http://forum.xda-developers.com/showthread.php?t=1060103&highlight=backup+file+locations+zune for details on how
3. Next, I got a backup file that didn’t belong to my phone and I edited the .xml files
- in the properties folder, you’ll find properties.xml
- I opened this file using notepad and change the #’s in the DeviceUrlId field to my unique device ID number
<DeviceUrlId>zune-tuner://windowsphone/XXXXXXXX%20-%20XXXXXXXX%20-%20XXXXXXXX%20-%20XXXXXXXX</DeviceUrlId>
- in RestorePoint\5372F2DE-F333-4717-9CB8-1846BE19900E\Data there is Manifest.xml
- I alsoopened this file using notepad and change the X’s in the DeviceId field to my unique device ID number
<DeviceId>XXXXXXXX - XXXXXXXX - XXXXXXXX - XXXXXXXX</DeviceId>
4. I connected my Focus to the computer and opened and waited for Zune to open
- waited for it to finish syncing
- left my Focus connected and Zune open.
5. Then I replaced the authentic backup files with the edited files from the other phone.
- Opened the backup file location on your computer from step 1
- Delete the existing Properties and RestorePoint folders
- Copied the Properties and RestorePoint folders from step 3 into this folder
6. I returned to Zune, went into Settings, then go to Update
- Wait for Zune to finish looking for an update
- It indicated that I had a restore point
- I selected to restore and followed the prompts
- All appears to be going well
7. On Step 3: Restoring Backup, the phone restarts, the and the Backup fails
- It spits out error code 801812E0
- I can't find anything on this code anywhere
At the beginning of step 3 it must be checking something in one of the other files?
IDK...
I do think this could work if we knew what Zune was checking that gives it the fail.
A quick look at the data files suggests to me that they may be encrypted. This would make sense, since otherwise you could overwrite the OS at a very low level by modifying your backup and then "restoring" it.
I bet the encryption key is stored in the device somehow, though.
GoodDayToDie said:
A quick look at the data files suggests to me that they may be encrypted. This would make sense, since otherwise you could overwrite the OS at a very low level by modifying your backup and then "restoring" it.
I bet the encryption key is stored in the device somehow, though.
Click to expand...
Click to collapse
they are encrypted and sighed against your imei and CID from the sd card.
and it could be that it is sighed online when you are downloading the update (but I don't know that for sure)
but the main problem is that you can't use another his backup because the activation email adress is stored in the backup.
and it is way to complicated to get that out because it is stored on to many parts of the backup.
so if there was a way to hack the encryption you could only use it on your own phone.
ceesheim said:
they are encrypted and sighed against your imei and CID from the sd card.
and it could be that it is sighed online when you are downloading the update (but I don't know that for sure)
but the main problem is that you can't use another his backup because the activation email adress is stored in the backup.
and it is way to to get that out because it is stored on to many parts of the backup.
so if there was a way to hack the encryption you could only use it on your own phone.
Click to expand...
Click to collapse
I don't think the email has anything to do with it.
I have tried all variables of restore files to phones with live activation set up and not set up.
With the false restore files, it fails the same regardless.
With restore files from the phone, it works the same, regardless of what live account is activated on the phone or in the restore.
Sent from my Focus using XDA Windows Phone 7 App
As I mentioned, it is not the way we can walk. One phone, one backup, another phone, another and so on. Sad but true.
well, FWIW, here are the 7008 backup files...
7008_Backup.zip
the file is 515 MB.
There is no Live account associated with the backup and I've already replaced the device ID info in the two xml files with X's
munkeyphyst said:
well, FWIW, here are the 7008 backup files...
7008_Backup.zip
the file is 515 MB.
There is no Live account associated with the backup and I've already replaced the device ID info in the two xml files with X's
Click to expand...
Click to collapse
It would've spared you some time, I did it before you and it's not working. As ceesheim said, they are tied to hardware.
I'm looking now to patch Zune to bypass that.
Thanks, I didn't see that. I hope the "clean" 7008 restore files are of use.
Is there the possibility to extract specific files ie those related to SMS and use them in another backup?
efjay said:
Is there the possibility to extract specific files ie those related to SMS and use them in another backup?
Click to expand...
Click to collapse
Not at the moment, as the backup files are encrypted. Different people (myself too) are working on various approaches, to try to access or unpack the rom files (from backups).
EnderPsp said:
Not at the moment, as the backup files are encrypted. Different people (myself too) are working on various approaches, to try to access or unpack the rom files (from backups).
Click to expand...
Click to collapse
Thanks for the reply.
I wrote something about this topic overhere.
EnderPsp said:
It would've spared you some time, I did it before you and it's not working. As ceesheim said, they are tied to hardware.
I'm looking now to patch Zune to bypass that.
Click to expand...
Click to collapse
it isn't zune that check it but the ULDR that validates it , so it doesn't bring you anywhere to patch ZUNE I think.
7008_Backup.zip
7008_Backup.zip multiuplood link please
ranya said:
7008_Backup.zip multiuplood link please
Click to expand...
Click to collapse
There is no way (yet) to use another phone's backup so a link would not help you.
Sorry to resurrect this thread, but maybe all we would need to do is change the activeid and the folder, that goes 8-4-4-4-12 with random numbers. Is there another 7008 backup to compare that number with? maybe all you need is the activeid for your phone, if phones have seperate active ids.
May seem like a silly question, but I've been a loyal titanium backup user for years. I just got my GN and am trying to get it to be a licensed version that I got that I've been using with my .txt file. However, even though I put it in the root of my SDCARD using root explorer, TB still thinks it's in free version mode. I'm sure you've figured it out, but for the life of me, I can't. Thanks in advance.
sonofabit said:
May seem like a silly question, but I've been a loyal titanium backup user for years. I just got my GN and am trying to get it to be a licensed version that I got that I've been using with my .txt file. However, even though I put it in the root of my SDCARD using root explorer, TB still thinks it's in free version mode. I'm sure you've figured it out, but for the life of me, I can't. Thanks in advance.
Click to expand...
Click to collapse
I just did the same thing last night. I didn't have any problems getting the license .txt file to work. But, you need to go into manage apps and clear the data for titanium backup if you opened it already without the license file being there.
The file was just improperly named. Your post jogged my memory of this problem I had before. Thanks for the help.
Have any of you tried to "protect" a backup with TB on your GN? I'm getting an error message.
Apps will backup, but just can't get protected.
I sent an email to the developer. He said that there is no ability to protect files on the internal "sdcard" but they're looking for a work around.
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
aukhan said:
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
Click to expand...
Click to collapse
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
mvattoy said:
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
Click to expand...
Click to collapse
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
aukhan said:
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
Click to expand...
Click to collapse
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
mvattoy said:
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
Click to expand...
Click to collapse
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
aukhan said:
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
Click to expand...
Click to collapse
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
mvattoy said:
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
Click to expand...
Click to collapse
first recommend you to flash stock and try see if you've got you IMIE .
mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
1st flash a stock rom and see whether u get imei and baseband back or not.. if it didnt get recovered then service centers can only help you as u didnt make a backup of efs..
There is a slim chance its not his efs,
I did pretty much the same as he to get root thru the toolkit, and had no network, I found I had no APN configured
Perhaps check this.
Settings... more settings .. mobile networks... acess point names.
Make sure you have something here.
if not you will need to search for the settings for whoever your provider is.
good luck
A|c
Hello,
New XDA poster, here... I've watched the intro video, and I've read the forum rules.
I'm not completely new to custom roms; I've previously flashed CM images on 2 other occasions, (on this same device, and 1 other.)
My question is: if I've lost my maguro's IMEI number (presumably by wiping /factory via CWM,) how screwed am I? I do not have a backup of /factory.
Here's how I got myself into this mess:
(Started from CM-10.1.2 or CM-10.1.3, can't remember.)
1. Updated recovery to clockwork-6.0.4.3-maguro
2. Factory reset (from inside recovery)
3. Formatted /system, /cache, /factory (immediately after starting that last one, I had a feeling it wasn't a good idea.)
4. Installed "cm-10.2-20131030-NIGHTLY-maguro.zip"
5. Installed "gapps-jb-20130813-signed.zip"
6. Rebooted
Everything worked peachy, except now my mobile service is permanently unavailable. Confirmed that I now have a generic IMEI number under Settings -> About phone -> Status.
This was a Play Store purchase; I am the original owner.
</ryan>
I have the same issue.
Did the /factory wipe on my phone from cwm. Among other wipes from the mounts menu.
Installed cm-10.2 ... Nightly
Here are the problems which I am facing.
1. The network signal indicator is blank & the phone reports emergency calls only. On my Vodafone's sim. ( also on tata DoCoMo & Idea sim cards).
2. Although the network signal indicator is blank 2g gsm mobile data is still working I.e. I can access websites, sync my phone with Google etc. Its just the call functionality is not working.
3. Tried another SIM from BSNL ( a local service provider in India). This sim works fine all the functionality ie call, sms , data is working on the BSNL sim.
If anyone has any suggestion how to fix this issue please help.
Sent from my Galaxy Nexus
I haven't done this with the Gnex, but this did happen with the i9000 and i9100 back then when moving from CM6 > CM7 and formatting from RFS over to EXT2 partitions destroyed my EFS folder. What I ended up doing was using Odin to flash back to stock from bootloader: the TAR images. I hope that if you flash to stock using Odin that you can achieve similar results. Remember that factory-images for Play Store models are "takju". Outside the US is "yakju".
OK let me try ODIN flashing.
Using the method & files from the following post
http://forum.xda-developers.com/showthread.php?t=2065470
Sent from my Galaxy Nexus
alpha-niner64 said:
I hope that if you flash to stock using Odin that you can achieve similar results. Remember that factory-images for Play Store models are "takju". Outside the US is "yakju".
Click to expand...
Click to collapse
Of course I'm willing to try anything that stands some chance of success, but I wonder: how could flashing Google's stock takju image-- that is the same for everybody-- restore an IMEI number that is different for everybody?
Solution...
Well kinda.
The issue is with Generic IMEI 004999010640000 most network providers have blocked this IMEI no. on their network, which is why the network registration fails & thus we get no network.
Their is a file nv_data.bin in 2 places on the device one is in /factory/nv_data.bin & the other is in /data/radio/nv_data.bin
The file in /data/radio/nv_data.bin determines the phones imei no. & the one in /factory/nv_data.bin is the backup.
In case the phone gets wiped or factory reset the system copies the file from /factory/nv_data.bin to /data/radio/nv_data.bin in order to determine the handsets IMEI no.
When you & I wiped the /factory/ in CWM it removed this backup file, thus on installation of any subsequent roms the phone was getting a generic imei resulting in network error.
If you have a NANDROID backup of the phone in an earlier state when the network was working correctly then restore from that backup & your network should be fine. I did & it restored my network.
Also if you are successful in getting your network & IMEI back I suggest backing up /data/radio/nv_data.bin & /data/radio/nv_data.bin.md5 to your PC because since the nandroid backup does not restore these files in /factory/ I am guessing any future wipe / rom upgrades will reset the radio to generic IMEI.
If you dont have a nandroid backup of a earlier good state of your phone I have no idea how to recreate the files.
in case you need it You can find your handsets IMEI no. in at the back of the phone below the battery.
The following links may help
http://forum.xda-developers.com/showthread.php?t=1570342
http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html
Brilliant post, gaurav1984.
Nope, no remaining backups at all. It seems odd to watch myself type those words, as I'm usually pretty zealous about backups generally. But I'm relatively new to CM, and in this instance my thinking was I wanted a completely fresh wipe; there was nothing I desired to save... or so I thought.
Since the consequences of wiping /factory are so dire, I think it would be a good idea if the CWM developers guard that particular action with a prominent red warning message.
... I might possibly have a Titanium Backup, from almost 2 years ago, somewhere. I wonder if that included nv_data.bin. Hmm...
</ryan>
Ryan,
take a look at the last paragraph on this page:
http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
Sounds like might be a viable option for you.
ryanvbissell said:
Brilliant post, gaurav1984.
Nope, no remaining backups at all. It seems odd to watch myself type those words, as I'm usually pretty zealous about backups generally. But I'm relatively new to CM, and in this instance my thinking was I wanted a completely fresh wipe; there was nothing I desired to save... or so I thought.
Since the consequences of wiping /factory are so dire, I think it would be a good idea if the CWM developers guard that particular action with a prominent red warning message.
... I might possibly have a Titanium Backup, from almost 2 years ago, somewhere. I wonder if that included nv_data.bin. Hmm...
</ryan>
Click to expand...
Click to collapse
Update...
@ryanvbissell any nandroid backup (no matter how old or whichever rom ) will do even if it is not CM.
You may try the procedure on the link above, but from what I have read Galaxy Nexus NV_data uses salted md5 checksums so that method might not work.
Also if you have the nv_data.bin & nv_data.bin.md5 files you can push it into /factory so that whenever you flash a new rom or do a factory wipe the system picks up these files from /factory & restores correct IMEI data.
You will need ADB & Samsung USB Drivers(only on windows) for this procedure to work, Please Google how to installing ADB
& If you are on windows installing Samsung USB Drivers for Galaxy Nexus. drivers for Galaxy Nexus™ (Verizon) Android Smartphone, work for the GSM variant as well.
On MAC you don't need the USB drivers, just install ADB.
Here is how
1. From CWM recovery -> mounts and storage -> mount /factory.
2. From your PC -> adb push nv_data.bin /factory
3. From your PC -> adb push nv_data.bin.md5 /factory
4. From Your PC -> adb shell
5. From Your PC -> # cd factory/
6. From Your PC -> /factory # chmod 700 nv_data.bin
7. From Your PC -> /factory # chmod 700 nv_data.bin.md5
8. From Your PC -> /factory # chown radio.radio nv_data.bin
9. From Your PC -> /factory # chown radio.radio nv_data.bin.md5
10. From Your PC -> exit
After this install a new ROM or do a factory wipe & your IMEI should be back & networks should work.
now any future wipe / rom upgrades will NOT reset the radio to generic IMEI.
I have done the same on my phone with successful results.
ryanvbissell said:
3. Formatted /system, /cache, /factory (immediately after starting that last one, I had a feeling it wasn't a good idea.)
Click to expand...
Click to collapse
I did the exact same thing, felt the exact same way, and on the same day too. And I had also purged all my backups at one point and decided to start over when this happened. Freaky.
@gaurav1984 - That was my solution as well. Luckily, it turned out I had an old lingering backup I made months ago on a network drive from the last time I backed up my desktop to reinstall Windows. Completely forgot about it until just a little while ago, and found out that a regular data backup (at least with TWRP) includes /data/radio, so it contained a good set of nv_data.bin and nv_data.bin.md5. I wound up doing exactly what you did but also pushed them to /data/radio/ and set the same permissions/ownerships there -- more of a spray-and-pray tactic since I hadn't seen your post at the time. Crossed my fingers, rebooted, and it worked! What a nerve-racking 24 hours.
Needless to say, those files are now backed up in several locations. Having /factory in the format list seems odd... should have to go out of your way to format something that important.
From what I found before I discovered my old backup, you'd have to buy a $200 magic box (which I think would just end up being an overpriced UART cable for this particular phone) and possibly some software to do an "IMEI Repair." I found some cheaper options from SRS Services through SamMobile (~$15US UART cable from China plus ~$35US to run a repair once), but it wasn't 100% clear if it could fix a formatted /factory partition with no backup whatsoever. I'm guessing it could since it requires a UART cable and the demo videos showed assigning an IMEI. Rebuilding these files is probably hard to come by since the same process can be used to clone another IMEI or change your IMEI to something other than what it's supposed to be, which is illegal in some countries.
mrbo said:
Ryan,
take a look at the last paragraph on this page:
http://www.droidviews.com/backup-and-restore-lost-imei-on-samsung-galaxy-devices-without-root/
Sounds like might be a viable option for you.
Click to expand...
Click to collapse
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
---------- Post added 3rd November 2013 at 12:14 AM ---------- Previous post was 2nd November 2013 at 11:51 PM ----------
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
rburrow said:
I did the exact same thing, felt the exact same way, and on the same day too.
Click to expand...
Click to collapse
Misery loves company.
rburrow said:
I did the exact same thing, felt the exact same way, and on the same day too.
Click to expand...
Click to collapse
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.[/QUOTE]
Agreed. My only surviving backup is a Titanium Backup, and it only includes APKs. So, I think my solution will be to buy a Nexus 5.
... And until it arrives, my email .sig will read: "-- SENT FROM MY ANDROID TOUCH", because obvious.
</ryan>
ryanvbissell said:
rburrow said:
I ran across a few of these guides for Samsung Galaxy phones as well, but I don't think they apply to the Galaxy Nexus... at least I couldn't figure out how to get it to work with our devices unless I was missing something important. I noticed they all mention Qualcomm and the I9250 doesn't have any Qualcomm stuff as far as I know.
Click to expand...
Click to collapse
Agreed. My only surviving backup is a Titanium Backup, and it only includes APKs. So, I think my solution will be to buy a Nexus 5.
... And until it arrives, my email .sig will read: "-- SENT FROM MY ANDROID TOUCH", because obvious.
</ryan>
Click to expand...
Click to collapse
Hah. I finally decided to order a Nexus 5 like an hour or two before I managed to wipe all the nv_data files simultaneously. My friend told me that I had a tiny tablet now when I figured out what I had done.
cardboardhome said:
I made the same mistake, but I do not think I have any backups. Do you have any idea if I can restore my IMEI? I know the value for sure.
Thanks for any help you can give.
Click to expand...
Click to collapse
If you really don't have a backup anywhere, I think your only solution is to send it in somewhere to have the IMEI repaired (either someone that says they can fix it, or to Samsung). Unfortunately it's more than likely going to cost money. The cheapest potential solution I could find was from SRS Services / SamMobile, where you have to buy a UART cable and pay to do an IMEI repair using their software. I have never used them so I have no idea how all that works out.
I searched quite a bit (albeit only for a like a day) for a free DIY way to regenerate or create a new nv_data.bin file, but I just couldn't find anything. The only thing I didn't try was an OMAP flash because I couldn't install the driver that came with the zip in Windows 8.1 64-bit, but I was already giving up at that point so I didn't go any further.
@ryan
I was just wondering about the ODIN method as posted on post no. 2 & 3.
When you flash your phone using ODIN it wipes the whole internal memory & recreates the partitions.
Thus we can assume all files gets wiped including those in the /factory.
So I was thinking if Odin recreates the whole filesystem as new maybe there might be some file or script or program .... In there which recreates the IMEI files as well.
Ryan if you feel up to it could you please do a Odin flash of your device ( since their is nothing more to loose ) & check if that somehow restores the imei.
If it does that might be really helpful to someone in the same situation as u in the future & you WD be able to resell your Gnex fully working.
Sent from my Galaxy Nexus using xda app-developers app
gaurav1984 said:
Ryan if you feel up to it could you please do a Odin flash of your device ( since their is nothing more to loose ) & check if that somehow restores the imei.
If it does that might be really helpful to someone in the same situation as u in the future & you WD be able to resell your Gnex fully working.
Click to expand...
Click to collapse
Good point. I originally passed up on the Odin angle because on a page that listed versions of Odin for specific phones, there was no suggested version for the i9250. But you have a good point; I really have nothing to lose. So I will try it, but it may take me a few days before I have time.
Meanwhile, I took my GN to a local 'CPR' cellphone repair shop, and explained my predicament. Their tech just shook his head sadly and said 'Only Samsung has the proprietary software to fix this.' I found that surprising because I think I've seen references online to some $200+ kit called SPT ("Samsung Phone Tools") which I thought was geared towards professional phone repair businesses. Oh well.
Sent from my ANDROID TOUCH... sigh.
</ryan>
IMEI
Odin flashing doesn't work
struggled today
dkkerry said:
Odin flashing doesn't work
Click to expand...
Click to collapse
did the same mistake of formatting factory today, it took me a day to find out my old backup dated back june 2013 made via cwm and finally phone is back to normal. Seems without backup restoring is impossible...maybe time to get nexus 5 for u
pvkiniyan95 said:
did the same mistake of formatting factory today, it took me a day to find out my old backup dated back june 2013 made via cwm and finally phone is back to normal. Seems without backup restoring is impossible...maybe time to get nexus 5 for u
Click to expand...
Click to collapse
Same happend with me today, and I dont even have a nandroid backup, as we both are from India you know its hard to get solved from a samsung service centre, can you please upload you CWM backup files??? so that I will try to restore those on my gnex
file too big
my backup file is around 2.1gb which will take me weeks to upload with the internet connection i have, may be if i backup the efs with some tools and send that img to u will that be useful...its really difficult to upload the whole backup
Utkarsh-ezzo said:
Same happend with me today, and I dont even have a nandroid backup, as we both are from India you know its hard to get solved from a samsung service centre, can you please upload you CWM backup files??? so that I will try to restore those on my gnex
Click to expand...
Click to collapse
pvkiniyan95 said:
my backup file is around 2.1gb which will take me weeks to upload with the internet connection i have, may be if i backup the efs with some tools and send that img to u will that be useful...its really difficult to upload the whole backup
Click to expand...
Click to collapse
ya i can understand that,
i think we domt have efs partition on gnex its located at /factory , so if you could share the file from /factory it would be great for me,
nv_data.bin, nv_data.bin.md5 , .nv_data.bak and .nv_data.bak.md5
these files from /factory would help me out..
you will need to use root browser or root explorer or adb shell....
Sent from my Galaxy Nexus using Tapatalk
Hello XDA. I have water damage on my motherboard, so I bought another one. I would like to keep the IMEI from the water damaged board. I made a copy of my EFS with TWRP and I was wondering is that enough to transfer the IMEI to the new board or do I need an NVeditor?
I could REALLY use some input on this.
I seen on ebay and youtube, they have a software program that changes it, I don't remember the name,
After researching for 2 days EVERYTHING that I'm reading is suggesting it's all about the EFS files. So I'm under the impression that restoring the EFS files from my TWRP backup is enough to restore the IMEI from the damaged logic board to the new one. I also have the software EFS Professional and made a copy of my EFS files through it. I just can't believe it could be so simple, especially with companies wanting to charge $65 min. to do it. IT CAN'T BE THIS SIMPLE.