I just got my new Mini Pro a couple days ago and realized that the CDF one my phone (1239-7457) doesn't match anything. Anybody have any information?
Is it a u20a or u20i, From where did you purchase it? That might give some clues. Also grabbing the firmware version from "Settings > About Phone" and posting the build.prop might yield other clues.
If purchased in the US it may be for the proper US kit, which seems to have just been released recently.
It's a U20a. I've been messing with the fw so I wouldn't be giving you the correct one. But I did buy it in the US.
Np, it's probably the proper US Kit if not bought through a grey market supplier or carrier. Looking for 911 in the emergency contact number for the build.prop would've been a dead giveaway.
So how would I go about resetting everything...? I've tried replacing the CDF number in build.prop with RootExplorer but it didn't do anything. At least I don't think it did...
Generally it's just change the cdf in the build.prop, reboot and get pc companion or se update service to do a repair install on the phone. Check the timestamp of build.prop after you save to make sure alterations were applied.
Wiping the content of the following directories beforehand usually helps.
For PC Companion.
Win XP/2k3 C:\Documents and Settings\All Users\Application Data\Sony Ericsson\SEMC OMSI Module\db\
Vista/Win 7 C:\ProgramData\Sony Ericsson\SEMC OMSI Module\db\
SEUS
C:\Program Files\Sony Ericsson\Update Service\db\
Related
I had/have bricked my X10 Mini Pro
I followed the instructions here
http://forum.xda-developers.com/showthread.php?t=743800
and after receiving NO errors and thinking everything was finished unmounted from the host machine and unmounted the sd card and re-booted the phone
Sadly it all went tits-up.
It booted into the locked screen and the reolution was way lower than before
The GUI was gone leaving only the activity/notification bar - the rest of the touchscreen was a fetching blue, with no applications, no corners, no nuffink.
Somewhere in this forum was a tip to start PCC and hold down the back and home keys, tap the power button and when the screen goes black connect the phone to the PC.
This gave me back a GUI but I have lost some Apps and more importantly it has booted into airline mode and no amount of turning 'Airline Mode' on/off with the power button will get rid of the airplane icon in the notification bar. So I can't get into my phone carrier nor any wireless networks.
So a few questions before I start again
Build.Prop file
changing numbers to have an unbranded phone for Australia ?
- is it just a matter of opening the file with gedit and changing the string with something from the list for Australia then saving or need I also change locale to AU ?
ok assuming that I only cut 'n' paste the 1234-1234, or whatever the number is I need to use to allow SEUS to update the phone for me, into the build.prop file then save it to copy from the SD card into the phone's system directory
( ./busybox cp /sdcard/build.prop /system/ )
I think that command roughly translates to " run busybox to copy the build.prop file on the card into the system sub-directory of the phone"
doesn't it ?
so, to continue this example,
I am in Australia,
I have a phone that used U20a firmware from this line
U20a WORLD-1-2-5 CDF1238-2298 1239-2226 3 AU/Black
I would cut the 1239-2226 and paste it into line #3 of the UK generic .prop file
ro.product.name=U20i_1238-0199
or do I change the line to read ro.product.name=U20a_1239-2226
or am I barking at the wrong tree ?
and
#68 ro.product.locale.region=GB
should that now read
"ro.product.locale.region=AU"?
hey mate hope this helps:
backup your build.prop first
open build.prop and replace the 1234-1234 values with the values directly after CDF, in this case 1238-2298.
do the following:
adb push build.prop /sdcard/build.prop
adb shell
su
mount -o rw,remount /dev/block/mtdblock0 /system
busybox cp /sdcard/build.prop /system/build.prop
exit
Now run update service.
it will ask you to connect your phone to the system. You will need to turn your phone off, hold the back button and connect the usb then after that just follow the prompts.
goodluck
Am I editing lines
#3 ro.product.name=U20a_1238-2298
AND
#8 ro.build.fingerprint=SEMC/U20a_1238-2298/SonyEricssonU20a/delta:1.6/1.1.A.0.8/1:user/release-keys
===
backup your build.prop first
===
I assume this is
./busybox cp /system/build.prop /sdcard/
Boo hoo hoo
That didn't work, having rooted the phone (I assume that when I connect it to my PC run CMD.exe and in the terminal run 'adb shell' then su the SuperUser application opens up in the phone to allow/deny is an indication that I have root)
I have edited the generic UK build.prop file to change it to an Australian Vodafone build.prop file ---I think ---
Exited out of the adb shell, exited out of the command line interface
unmounted the phone from the host machine
unmounted the client - the phone
shut down the phone
removed the battery for at least 5 seconds
during which time I completely removed all traces of SEUS using a Windows application called CCleaner
and reinstalled
opened the Update Programme
put the battery back in the SE phone
held onto the Back Button as if my life depended on it
connected the phone to the PC
SEUS says ..........
wait for it ..............
No new software available, try again later
I may well be the last Australian X10 mini pro owner running Android 1.6 and am getting pretty frickin' sick of being told by Sony that there's nothing new for me
i had the optus firmware but since i live in china now i have been using the chinese firmware. do system restore and see how that goes, otherwise get the optus system installed and update it...but as far as i know everybody should be upgraded to 2.1 by now...
Also all you have to do is just edit the build.prop and restore the original firmware through pc companion... and then try to get the 2.1 update hope that works mate
saywot said:
No new software available, try again later
I may well be the last Australian X10 mini pro owner running Android 1.6 and am getting pretty frickin' sick of being told by Sony that there's nothing new for me
Click to expand...
Click to collapse
You should have used "repair". That will work.
vlissine said:
You should have used "repair". That will work.
Click to expand...
Click to collapse
There isn't a 'repair' option any more with SEUS
and I keep getting the "No new software for your phone" message when attempting to repair using PCC
I'm guessing that I need to edit something else because I have some sort of a VFE file system version
Can I edit the firmware version in the build.prop file to something else
- then ask PCC to repair ?
Hmm
I just did the HBBHBHHB shuffle and see that in the software info section there appears to be an inconsistency
there is a different identifying strings of numbers for
- Phone software version
- S1 Boot Version
- ETS Sofware Version (whatever that is !!)
- Customization Version
I give up
I have edited the build.prop file with quite a few CDF numbers
re-booted
connected to SEUS
only to be told
"there is no new software for your phone"
I am starting to think that there will never be any 2.1 juiciness
I've tried Telstra AU, I've tried 3 Au, and Vodfone
- nothing and am now at my wit's end
And it's not as if this forum is bubbling over with suggestions as to the reason why a rooted phone can't have different firmware installed so it may have an OS upgrade
vlissine said:
You should have used "repair". That will work.
Click to expand...
Click to collapse
well, there's a problem with that
The only 'repairing' is done with PC Companion
I have un-installed/re-installed that POS about 4 times and now it's throwing
"Unable to install or start phone software update components" at me
I decided to just dump the generic UK U20i build.prop file into the system directory and overwrote whatever I had there (the older one was saved as build.prop.bak)
This still didn't get me any software updates from SEUS - if that's what Sony is calling the next Operating System.
So apart from copying and pasting the whole build.prop file I want to use and asking what EXACTLY needs to be changed.
I have a question or two
-- "VFE-1-8 1.1.A.0.8" how can I get it changed to 'World 1-2-5 ?
-- and no matter what I do to the customisation version using an edit or two of /system/build.prop the software version stays the same and this is why I think I keep getting a "No New Software For Your Phone - try again later" from both SEUS and PCC
and the Model Info always reports U20a
as always any help or suggestions will be gratefully received
saywot said:
well, there's a problem with that
The only 'repairing' is done with PC Companion
I have un-installed/re-installed that POS about 4 times and now it's throwing
"Unable to install or start phone software update components" at me
Click to expand...
Click to collapse
There was no need to install and reinstall PCC, you could have simply deleted the directory containing downloaded firmware, so that it will download the correct one.
You are doing lots of unnecessary things, and the way you do it takes you nowhere, since instead of simply following the guide which has been posted and tested by practically everyone on this board you start fiddling with wrong parts of the system.
My sincere advise to you is spend 10 euros and get it reflashed by these guys http://www1.davinciteam.com/index.html
Good luck.
There was no need to install and reinstall PCC, you could have simply deleted the directory containing downloaded firmware, so that it will download the correct one.
You are doing lots of unnecessary things, and the way you do it takes you nowhere, since instead of simply following the guide which has been posted and tested by practically everyone on this board you start fiddling with wrong parts of the system.
Click to expand...
Click to collapse
Now you tell me !
I know what I have been doing is futile and wasting my time.
But the guide is NOT simple for some of us less-talented people.
It doesn't say whether to replace all instances of the xxxx-xxx number in the build.prop file or only one,
I'm still not clear where there is a mention of CDFxxxx-xxx yyyy-yyyy whether I should use xxxx-xxxx or yyyy-yyyy in editing the properties file
Also the phone is a u20a phone, the UK Generic file is for u20i devices, and the guide doesn't make any distinction between the different hardwares - and they are different
In which directory does PCC keep the downloaded firmware that I am to delete?
'Dashboard' 'Drivers' 'Languages' or 'Skin' are the choices of directories, the rest of the C:/Program Files/Sony Ericsson/Sony Ericsson PC Companion/ folder are individual files - dlls exes etc etc
So to start again
I am about to upload (via the CLI in Windows) so
one last question (which is really the first question)
which line do I change in the build.prop file
- I am now assuming from the tone and content from #vlissine that I am changing too much so it's one line with one new number
and is it the string of numbers attached to the alphabetic CDF or those immediately following the CDF alphanumeric string in the u20a listing?
This is sort of the firmware I'm after
U20a WORLD-1-2-5 CDF1239-5023 1238-9150 Telstra AU/Black
which is to ask - do I use "1239-5023" or "1238-9150"
B.T.W.
if the phone has 1.1.A.0.8 firmware
and the build.prop file has 1.2.A.1.174
doesn't that create some sort of 'inconvenience' for me ?
Looking for someone to help test a potential fix (worked for my captivate).
If you have discovered after returning to stock that your phone has the WRONG PRODUCT CODE (and possibly a generic IMEI) this might be worth a try please do following:
1. Post your product code (can get results using SGS Toolbox free from market).
If anyone has this issue we can move forward once someone has posted step 1 and would like to try to restore correct product code.
PS - Product Code is stored in your nv_data files and some have had issues with the files being corrupted with an improper product code that prevents phone from connected to kies.
I have wrong IMEI number and have no idea how to find product id (sgs tools have no option of showing product code and sgs toolbox won't install on my phone)
In US, I have a Windows 7 machine with Mini Kies installed. Using Regedit, look under:
HKey_Current_User, Software, Samsung, KiesMini, FUS (look for the product code line).
In my case the Product Code entry is: SGH-T959ZKBTMB
BTW, to the OP, I have the unregistered device error even though the IMEI and Product code match to the box and phone labels, hone is registered with Sammy, etc. Don't know if that helps or not, but...
bames said:
Looking for someone to help test a potential fix (worked for my captivate).
If you have discovered after returning to stock that your phone has the WRONG PRODUCT CODE (and possibly a generic IMEI) this might be worth a try please do following:
1. Post your product code (can get results using SGS Toolbox free from market).
If anyone has this issue we can move forward once someone has posted step 1 and would like to try to restore correct product code.
PS - Product Code is stored in your nv_data files and some have had issues with the files being corrupted with an improper product code that prevents phone from connected to kies.
Click to expand...
Click to collapse
Does this occur when returning to stock using odin?
How can I recreate this issue?
Hello all,
Not a great first post, but I have a problem, that I cannot solve myself.
I bought LUMIA 800 from a guy on ebay, really good offer(ofcourse), the phone was in good condition, all functioning. Checked the IMEI - not stollen. After taking it home, I noticed that I cannot log into microsoft live, facebook and twitter, from the add new account menu. It keeps giving me - there is an error, please try again later. However, day after that, the phone gives me a message - this demo phone is going to be reset. After that reboots, with all my data formated and starts installing content, like some demo contacts, messages and etc. Also a promo video is played, while I`m loading it.
So, in short - is there a way to get that phone to function normally? I tried both formats, from the menu and with the 3 buttons, it always starts loading the demo contacts and etc.
Any help will be greatly appreciated!
Pavel
ok, did my homework and searched the forums. I will try with standart debranding method, hope it works.
you can flash it using NCS (Nokia Care Suite). I will upload a handy tool for you. wait a moment....
here you can download the tools: http://www.multiupload.nl/91Y8NK6L7E
greatly appreciated Tim! thank you
Hi,
I also got one of those demophones and I tried Tim's method but When I do Step: 20 and Step: 21 I do not see the newer firmware there.
The line where it should be is plank.
I have downloaded firmware from navifirmplus and place it to that exact place what it is on Tim's document: C:\ProgramData\Nokia\Packages\Products\RM-801 without any subfolders.
But on my PC I had to make that products folder too, there was none when I first time navigate to that folder, I check File -> setting from product support tool for store and there that folder is right but I do not see that newer firmware, so can anyone help?
you must run the applications under Administrative rights. so right click on the NCS and click: "Run as Administrator"
otherwise the program doesn't have access to the c:\programdata\......
most accounts have administrator rights, but if you have UAC (userAccountControll) enabled on your computer than the error that you describe will come.
Hi tim!
I tried with administrative rights, now effect, still do not show "new software version"
Does that Product Code have to be same on downloaded firmware and that it is already on phone? caude in phone I have 059N394 and firmware I downloaded is 059N341
You solved your own problem ;-).
yes that's the issue, make the productcode that you downloaded the same as the productcode of your phone, and it will work.
in NaviFirm there is not a code with "059N394", I would download the firmware that is applicable to my country and color, and most matching with the productcode of the phone.
sorry for my bad english....
Please hit the "Thanks" button if I helped you....
Thanks! ur a MAN!!!
It worked!!
Please have you got someone firmware NOKIA LUMIA 800 RM-801 for Nokia Care Suite ?
Thank you very much for your help.
David
Hello,
I used my NL920 with Portico update and I didn't encountered problems with it like is "black screen of dead";
all the apps were normal and the live tile updates for the apps and for the system worked like charm.
After the Amber was available for my phone wasn't available the OTA update; even after a month ))))
So I download the firmware by it's original product code via NCS and I flashed it.
I saw all the new features with camera, calls blacklist, fm radio etc but in the same time the problems came out:
live tiles doesn't work anymore, the browser can't open new tabs on some sites, forums; the browser can't remember the username and the pass like was in previous version; the update for the operating system (storage checker and all the others) doesn't work anymore.
Any idea how to solve this issue because is very annoying;
should I have to write another firmware in my phone like the developer version or other?
My original rom is unbranded german rom.
Thanks!
MarianG said:
Hello,
I used my NL920 with Portico update and I didn't encountered problems with it like is "black screen of dead";
all the apps were normal and the live tile updates for the apps and for the system worked like charm.
After the Amber was available for my phone wasn't available the OTA update; even after a month ))))
So I download the firmware by it's original product code via NCS and I flashed it.
I saw all the new features with camera, calls blacklist, fm radio etc but in the same time the problems came out:
live tiles doesn't work anymore, the browser can't open new tabs on some sites, forums; the browser can't remember the username and the pass like was in previous version; the update for the operating system (storage checker and all the others) doesn't work anymore.
Any idea how to solve this issue because is very annoying;
should I have to write another firmware in my phone like the developer version or other?
My original rom is unbranded German rom.
Thanks!
Click to expand...
Click to collapse
Your Phone must be disconnected from PC during these steps.
Go to the Folder option and Uncheck these options.
(I use windows 8.1 so this options exist in all type of windows, maybe just slightly different)
1-Show hidden files and folders or drives
2-Hide protected operation system files
Then go to :
C:\ProgramData\Nokia\Packages\Products\rm-821
( Attention: rm-821 or rm-820 depends on your phone) mine is 821.
Check if there is Rom and Firmware files over there, rm-821 folder must be around 1.23 GB.
If yes then you need Nokia Care Suit (2012.45.4.5)
Attention : older versions does not support Lumia 920
Download it from : HERE
after installation go for : C:\Program Files (x86)\Nokia\Nokia Care Suite\Application Launcher\bin
and click on "ApplicationLauncher.exe" from opened application choose "Product support tool for store 5.0"
In the new opened page go to:
Files - Open product and choose your Lumia 920 (Attention: be careful on your RM, if you have rm-820 or rm-821)
A red Lumia 920 will appear.
Down there you may see "Programming" open it and choose "Recovery"
it should automatically find your ROM from mentioned folder above.
it should be something like: 059R*** RM-821 VAR *** 3047.0000.1326.2002
Press start and follow the instruction ... DONE
My NCS version is 2013.38.3.2. Lumia 920 RM-821. Haven`t used it yet though but it seems compatible.
azithro said:
Your Phone must be disconnected from PC during these steps.
Go to the Folder option and Uncheck these options.
(I use windows 8.1 so this options exist in all type of windows, maybe just slightly different)
1-Show hidden files and folders or drives
2-Hide protected operation system files
Then go to :
C:\ProgramData\Nokia\Packages\Products\rm-821
( Attention: rm-821 or rm-820 depends on your phone) mine is 821.
Check if there is Rom and Firmware files over there, rm-821 folder must be around 1.23 GB.
If yes then you need Nokia Care Suit (2012.45.4.5)
Attention : other versions does not support Lumia 920
Download it from : HERE
after installation go for : C:\Program Files (x86)\Nokia\Nokia Care Suite\Application Launcher\bin
and click on "ApplicationLauncher.exe" from opened application choose "Product support tool for store 5.0"
In the new opened page go to:
Files - Open product and choose your Lumia 920 (Attention: be careful on your RM, if you have rm-820 or rm-821)
A red Lumia 920 will appear.
Down there you may see "Programming" open it and choose "Recovery"
it should automatically find your ROM from mentioned folder above.
it should be something like: 059R*** RM-821 VAR *** 3047.0000.1326.2002
Press start and follow the instruction ... DONE
Click to expand...
Click to collapse
But I already flashed my phone via NCS with Amber update;
The flashfiles folder is in c/ program files/ nokia/ phoenix/ products/ rm-821;
I made this path for the flashfiles because all other products are there installed.
Also I modified the path in the NCS.
You tell me that I need to flash it ONLY with the version 2012.45.4.5 ?
I'm using Xp sp3 on my pc and the version of NCS I don't remember right now but I think is higher than the version that you mentioned..
I'll check tomorrow when I'll be at the office and I'll reply.
Thanks!
MarianG said:
But I already flashed my phone via NCS with Amber update;
The flashfiles folder is in c/ program files/ nokia/ phoenix/ products/ rm-821;
I made this path for the flashfiles because all other products are there installed.
Also I modified the path in the NCS.
You tell me that I need to flash it ONLY with the version 2012.45.4.5 ?
I'm using Xp sp3 on my pc and the version of NCS I don't remember right now but I think is higher than the version that you mentioned..
I'll check tomorrow when I'll be at the office and I'll reply.
Thanks!
Click to expand...
Click to collapse
Phoenix?
in XP i think the ROM is in: C:\Documents and Settings\All Users\Application Data\Nokia\Packages\Products\rm-821
Maybe you downloaded ROM from unofficial page, is not it?
If yes, please use NCS [go to download option enter product code , exactly as your device is] then NCS will download it for you.
Attention: Did you changed you product code recently?
if you unlock your phone you will be able to change product code. did you do that?
if yes please recover your product code to original state.
Before doing this please backup your rm-821 folder save it as zip then:
go to .....Nokia\Packages\Products . stay in product folder and delete everything inside the product folder.
then try to download your rom from NCS
and yes when you download NCS 2012, it says there is update for your NCS, about 140 MB i think !!!
let it update.
Sorry but why you have phoenix ? I do not thing that's a true installation path !!!
better to uninstall your unofficial Nokia software and Note that remove all folder about Nokia in appdata and program files
both of them:
C:\Program Files (x86)\Nokia (C:\Program Files\Nokia )
C:\ProgramData\Nokia
or in xp
C:\Documents and Settings\All Users\Application Data\Nokia
Flashing a different Color ROM also may cuz bugs in your phone (eg: installing Lumia Red Color on Lumia White) plz be careful about product code.
Your ROM indexes must show as what wrote on Lumia Box (eg: you will see something as : this product made for Netherland and has 2 year warranty or guaranty in this country ) it means your phone has EU brand.
if BOX and installed ROM is different then your product code changed.
any more question? please ask...
Regards
---------- Post added at 12:26 PM ---------- Previous post was at 12:15 PM ----------
gee2012 said:
My NCS version is 2013.38.3.2. Lumia 920 RM-821. Haven`t used it yet though but it seems compatible.
Click to expand...
Click to collapse
Yes Bro I forgot to mention 2012.45.4.5 and above.
Ok. So here's the deal:
My SGS3 I9300 exynos phone did the famous IMEI 0049 and SN null trick.
I cannot say what precipitated it but is simply stopped registering on the network, so no calling or data. All other functions operational.
After much searching and reading, I settled on flashing the stock 4.3 back. This succeeded only in doing absolutely nothing to alleviate this issue. I wiped the entire phone. Maybe I missed a critical section wipe, but since the stock ROM overwrites all? the CSC/BL/MODEM functions I thought it would set the default for EFS (which I believe is where these critical data live). I'm not a programmer so I cannot say diddly about the architecture and interrelationship of OS files, but I am technical and I know how SW and HW does what it does.
This phone is my own and I have all the rights to it.
I had loaded RRemix ROM a loong while ago and it was functioning fine. Probably a corruption of the EFS due to battery contact being loose. This is in my mind the most likely cause as the system may be accessing the EFS files, say making a call, or accessing data, and the power drops out and voila! Corruption. But again this is theoretical.
Needless to say I tried the usual hocus-pocus out there with no avail.
Getting to understand the system better it seems obvious that these critical identification numbers are hard-coded into the chips on the phone. Which explains the ability to 'fix' them with JTAG and other cable/box solutions and SW. However, I cannot see how the SW loses the ability to read the IMEI/SN that is hard-coded (fused?) into the main-board.
All my research pointed to the EFS files having something to do with this.
Way back when I loaded the custom ROM I did not come across the 'backup your EFS' as a necessary step, so I had nothing to go back on.
And loading the stock 4.3 ROM back on and not having that fix the issue, led me to believe something else was up.
Somewhere in the guts of this phone something is screwing up the layer between reading the registers where the numbers sit and the software layer that reports the numbers.
So, much searching led to the nv_data.bin file being a key component in all this fiasco.
Now, before I say any more, I believe that describing the next steps could be a big no-no here.
Now, understand, all I want to do is get MY personal device working again. I have the SN and IMEI numbers on the physical device.
Sure, I could have stolen it and am attempting to change these to avoid prosecution. Anyone can say anything online.
Therefore, before I can proceed, I need advice from moderators and VPP to either say 'Yes you may post this info' or 'No. Go away'.
Am I allowed to do the following:
1) Describe how I restored my IMEI (Not changed, overwritten, or subverted to my limited knowledge)
2) In the case of 1 not allowed, post the link to where I found the info to achieve this.
3) Submit the 'fix' to a moderator or developer to check whether this is indeed and restoration or a change.
If it's a restoration of existing functionality, I cannot see how this could be a problem. If its changing something, then it's a whole other sack of ferrets.
My reasons for posting are that xdadevelopers has given me years of joy with my SG devices. (Yes, I have the whole range exclusively) Many ROMS, customs, fixes, hints and saves deserves something back, and the difficulty in achieving this particular fix, warrants it.
But I don't want to break any rules, this being my first post.
So, please let me know what I can do to help others stuck in this position...
You can find it if you have the correct search parameters. Perhaps I can say that instead?
Thanks.
And thanks to all who have helped over the years.
T
[Edit] Just to clarify, the solution requires no special HW or 'boxes'. You do need root, however, and a hex editor. I had a reply explaining the use of Octoplus, which requires credits and registration. You will need none of those.
I can't speak English but I will try.
1- flash stock firmware.
2- root your device s3 .
3-in the web download " octuplus crack box"
4-in youtube see how install " octuplus crack"
5- before install stop your antivirus PC
6- open octuplus and connecte your phone with PC
7- chose your device i9300 .
8 click repair imie
9 click read info and do what OCTU said to do.
10- click repair or write the true imie in your device ( remove battery to see)and click repair.
11- restart phone .
12- see: call work fine
13- in phone go to mobile network\ access point names\ apn's
14- write your network.
TrinityTrip54 said:
Ok. So here's the deal:
Repair is ok Change or Modding is now:good::good::good:
Click to expand...
Click to collapse
How to restore corrupted or null 0049 IMEI on SGS3.
Right.
Thanks to the moderators for agreeing to let me share the solution. :good:
Thanks to the reddit poster who found this solution. I don't know how the hell you figured this out, but big-ups to you. For privacy I will not mention names or addresses.
You do need a rooted phone and I cannot assist anyone without root as I have not tried it.
Whether this only works to restore a corrupt IMEI or change it, I cannot say, but it managed to restore my existing one.
Preparation: Get your IMEI number from under your battery compartment. Say your IMEI no. is: 123456789101213, write/type it in the following fashion: 1 23 45 67 89 10 12 13
Now some funky transposition: Excluding the first number, transpose the subsequent pairs of numbers so that you have: 1 32 54 76 98 01 21 31. Can you see it? Swap 23 to get 32. 45 to get 54 and so on.
Now add 08 to the beginning and add A after the 1 so that the completed number is: 08 1A 32 54 76 98 01 21 31
Now you will need:
Rooted Galaxy S3 (This may work for all android devices that have an EFS folder. If anyone can confirm that would help others.)
Hex editor (PC based or Android app) - PC is faster and easier. I used hex workshop trial version but I'm sure any editor will do. I used the default install configuration.
USB Data cable (if using PC editor mentioned above)
You should probably back up the EFS folder entirely, just to be sure.
Using your favorite root explorer browse to root/EFS folder and copy the nv_data.bin file to an accessible area in sdcard. I use a /sdcard/Downloads folder.
Either open the file with your hex editor app or transfer the file to PC where you can open it with your hex editor program.
Open the file and jump to address 00550.
Now, get your modified IMEI number from the prep steps above and enter the values in the ASCII TEXT window to the right, NOT the HEX values window to the left. This may be different for other editors but hex workshop works like this.
Double check your address and entered data. When satisfied, save the file and transfer back to the phone if copied to PC.
Now, place the phone in Airplane mode, turning off the cell radios.
Go to the EFS folder and rename the original nv_data.bin file to something else. I used nv_databak.bin.
Copy the modified nv-data file into the EFS folder.
Turn off Airplane mode and do a full reboot.
Your IMEI number should be restored and cellular functions should work.
My previously garbled serial number was also restored.
I hope this works for you. I have no knowledge of any other method as I did not delve further into trying other numbers or such. I can't assist any more other than further clarifying the steps above if you don't understand something.
If anyone can decipher what is going on here, I would love to hear about it. I suspect something between the HW and SW layers is getting garbled or corrupted and this kick starts the process to get the correct data again.
Maybe.
May also contain nuts.
Hastalavista.
T
THANKS FOR POSTING THIS HERE!
I have this Samsung Galaxy S3 that I bricked 4 years ago and never wanted to sell it or even try to give it away. I searched for months for a frekin solution to this problem. Yesterday night i decided i wanted to try and install custom roms on it and so i wanted to give another shot at this stupid issue i had with the lost IMEI before doing so...and BAM! Today it's fixed!
I'm so thankfull I wanted to post here so that you know that you helped at least one person with this
Thanks a bunch!
@TrinityTrip54
Hi,
can you confirm that this is a permantent solution and remains when flashing new (custom) ROMs? Or is it just for the current installed ROM?
And I am having an issue with "jump to address 00550" in Hex Workshop. There is no address like this, just 540 and the next one is already 558. When inserting 00550 in the goto search field of Hex Workshop it jumps to 210. Any idea?
thanks anyway.
bert