Droid X (and other moto droids) ESN and MEID correction/repair SOLVED

[Chris Wiedmaier]

Has anyone used this method on a bionic? I've got a bionic Id like to use on metro but it's locked down tighter than fort knox. and of course you can't add an imei to metro's database...

[cellperfection]

I cant get any of the links to work. does anyone have a good one? Id really appreciate it!

[cellperfection]

I cant get any of the links to work. Do u have another one I can try? Id really appreciate it!

[wke102]

Thanks for the share bro

[mrx6666]

As has been mentioned, the tricky part is getting the scripts to start up at boot, and on ROMS with different boot structure the posted methods can fail.

On stock gb, the file that matters is install-recovery.sh, the other script starting files aren't needed (and don't do anything on stock ROM, may be useful on other ROMS).

<Scripts that need starting>
esn.cfg
em-droid
mid.cfg
mm-droid
emd
<Start at boot method>
install-recovery.sh

to be in the correct locations, with correct permissions.

To use on CM4DX which is a 2nd init ROM or other ROMS with different structures the best method is to figure out how to load a custom user script on boot for that ROM.

Some have the feature built-in, like CM4DX:

Use root explorer to make/edit the file userinit.sh in /data/local
to have the following lines:

#!/system/bin/sh
sleep 20
/data/emd

This will almost always get the script to start at boot and as a bonus doesn't get overwritten when flashing a new version of the ROM.

On other ROMS look at the filestructure to figure out the best way to start at boot if one of the provided methods doesn't work.

As an additional tip, setting the [INTERVAL] field in *.cfg files to be 90 in one and 95 in the other tends to minimize crashes.

Finally, it is possible to have the scripts running correctly but the phone meid showing incorrectly through the android gui--it's all about the timing of loading the scripts.

Other than the details here about which files are needed see the readmes of the earlier post

[laptopfreek0]

Trying to get this to work on the bionic, but no matter what I cannot scan the locations of memory, nor can I read them. Any idea on how I might be able to achieve this?

[nwashi23]

YOU think this will work on CM9 for the droid x?? because autostart doesnt support it

As has been mentioned, the tricky part is getting the scripts to start up at boot, and on ROMS with different boot structure the posted methods can fail.

On stock gb, the file that matters is install-recovery.sh, the other script starting files aren't needed (and don't do anything on stock ROM, may be useful on other ROMS).

<Scripts that need starting>
esn.cfg
em-droid
mid.cfg
mm-droid
emd
<Start at boot method>
install-recovery.sh

to be in the correct locations, with correct permissions.

To use on CM4DX which is a 2nd init ROM or other ROMS with different structures the best method is to figure out how to load a custom user script on boot for that ROM.

Some have the feature built-in, like CM4DX:

Use root explorer to make/edit the file userinit.sh in /data/local
to have the following lines:

#!/system/bin/sh
sleep 20
/data/emd

This will almost always get the script to start at boot and as a bonus doesn't get overwritten when flashing a new version of the ROM.

On other ROMS look at the filestructure to figure out the best way to start at boot if one of the provided methods doesn't work.

As an additional tip, setting the [INTERVAL] field in *.cfg files to be 90 in one and 95 in the other tends to minimize crashes.

Finally, it is possible to have the scripts running correctly but the phone meid showing incorrectly through the android gui--it's all about the timing of loading the scripts.

Other than the details here about which files are needed see the readmes of the earlier post

[notideportes]

Hello, I tried the download links but I just get a blank screen. Any thoughs?

[NavedIphone]

Firstly Power off the Droid and then Remove the battery and the ESN/MEID is located in the battery compartment

[super coffee]

Hello all!
Has anyone figured out the correct mem addresses for the OG droid? I have one myself, but I can't get CDMA WS to scan the memory. It throws me one of those "The phone did not answer" messages, or something like that.

[duck95]

Thanks to everyone for the script and the help, but I'm stumped on the hex addressing.

The hex addressing in the Read Me doesn't match the addressing in CDMA workshop. Is there a way to convert it?

Also, when I do scan the phone (Droid X) memory, the phone reboots when it finds a portion not readable. Is there a way to avoid this? Does anyone have the readable ranges?

[pnonu23]

Hi Im just now getting a droid x from ebay, didnt explain that it has bad esn, I have a droid2 but need steps on converting #s. can sum1 pm me with sum instructions on getting started its on 2.3.3

[band8266]

Check out some chinese forums for updates a better ways to do this. in search engine type "挂EM"
Its all pretty straight forward put the files in /data, change to your ESN, then run the script.
For the locations you probably dont need to change them, use the default:
[Addrs]
0x00325F8C
0x0032C78C
0x006AE674
0x006BB9DC
Works for my Droid 2

Oh maybe its just because I am in China but I only use the ESN not the MEID?

[majunee]

Check out some chinese forums for updates a better ways to do this. in search engine type "挂EM"
Its all pretty straight forward put the files in /data, change to your ESN, then run the script.
For the locations you probably dont need to change them, use the default:
[Addrs]
0x00325F8C
0x0032C78C
0x006AE674
0x006BB9DC
Works for my Droid 2

Oh maybe its just because I am in China but I only use the ESN not the MEID?

Can you please explain what they write there in English I've been trying every method on my motorola photon with no success

[band8266]

Can you please explain what they write there in English I've been trying every method on my motorola photon with no success

I only change the ESN, (MEID I guess is not needed for China Telecom).
Using the default values above , and using the esn from an old samsung in the esn.cfg.
I only use 2 files, esn.cfg and em-droid.
Using ROM Toolbox, root browser I move the 2 files into /data with 0777 permision ( all checked ) then I press on em-droid and tell it to open it as a script file and it executes and gives me all written OK.
The only way for me to tell that it is working is I can actually call using the network.
A third file is possible to get em-droid to run at boot-up. ROM Toolbox has a scripter function that allows you to import or create a new script. All that script says is /data/em-droid Then click it to set at boot.