[GUIDE] Create a Fake IMEI for the Kindle Fire

Search This thread

MaxRabbit

Senior Member
Oct 21, 2010
778
227
Austin
Why do I want this?
Some apps do not work properly without an IMEI. The example app that I ran into is the XDA free application. Without an IMEI, the XDA app crashes when logging in. I believe it may also affect Terminal Emulator, causing it to force close on launch. The Kindle Fire, at least when running CM7 (not sure about stock), does not have an IMEI built in. Test yours by typing "*#06#" in the dialer.

Prereq's
Ensure the Kindle Fire ADB drivers are installed. The Kindle Fire Utility installed them for me.

Step 1
Download DizzyDen's IMEI generator.

Edit .ini to modify build.prop to stock Kindle Fire device identification (optional step)
(Use if you have issues with the Market or Amazon Appstore allowing you to download apps)
Settings:
Device_Manufacturer = TI
Manufacturer_Device = blaze
Device_Model = Full Android on Blaze or SDP
buildpropedits.jpg


Step 2
Run the program! For the first option, asking about dev's rom, select "no."
devornot.jpg


Choose "yes" for in-place upgrade.
inplaceupdate.jpg


It will pop up saying "Failed to read MAC address."

Ensure that your serial number was found and the IMEI is a correct 00-#### (series of numbers) format.
imeioutput.jpg


If all is correct, push to device:
pushtodevice.jpg


You must run it again on every ROM update!

FAQ
Q: Anything else this program can do?
A: Look in the !IMEIme.ini file, there are options for spoofing the device manufacturer, etc.
The following is the relationship from the ini to the build.prop settings:
Device_Manufacturer edits the ro.product.manufacturer
Manufacturer_Device edits the ro.product.device
Device_Model edits the ro.product.model

Q: Does this program support ICS?
A: DizzyDen says that it should.

Q: I've heard messing with IMEIs is illegal.
A: DizzyDen's program generates an IMEI with a 00- in front, indicating that it is a test IMEI. No illegal spoofing of a real phone is going on.

Q: Is there any way to add an IMEI to a ROM before flashing?
A: Yup, just choose "Yes" to "Are you planning to update a dev's ROM zip file?" and choose your ROM.

Q: Ran it, and under system > About Tablet > IMEI it shows as Unknown.
A: Normal, test with *#06# in dialer.

Please consider clicking a "Thanks" to me and to DizzyDen!
 
Last edited:

treo750ii

Senior Member
Sep 16, 2009
120
13
I've tried the free version on CM7.. FC QUITE A BIT!!! Will try this when I get off of work. Great work btw

Sent from my SGH-I897 using XDA App
 

G1ForFun

Retired Forum Moderator
Feb 1, 2010
2,975
294
Nice work, when I was on CM7 (now am back on stock kindle rooted) I was unable to use the XDA Free app at all because it kept force closing, though like others mentioned, the premium app worked fine.
 

ibleo02

Senior Member
Sep 22, 2008
79
11
Texas
Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?
 

DizzyDen

Senior Member
Feb 7, 2011
1,301
567
Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?

No... it won't cause apps to show up that don't show up... BUT

With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.

You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.

You could try the default KF info and if that don't work... make it mimic your Evo

And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.

One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.
 
Last edited:

tduermeier

Senior Member
Oct 8, 2010
81
8
Boulder, CO
So I'm not sure if I'm doing something wrong here, but for whatever reason !IMEIme cannot recognize my device's serial number. I have tried re-installing drivers, restarting my computer, restarting the kindle, elevating adb first, and nothing seems to be working.

Every time I run the program it says it cannot detect the serial number, nor the MAC address, then it tells me to input an IMEI manually. Judging by the original instructions, it is important that the tool recognizes my device's S/N before continuing. Any advice?

Thanks,

td

Edit: Just for more info, I'm running stock 6.2.1 with root. I tried a big ordeal just now with my drivers to no avail. It seems like the tool is not properly communicating somehow, though adb is certainly communicating fine.

I'm doing these steps:

1) connect kindle
2) select "Disconnect" when the usb transfer option appears on the kindle
3) run "!IMEIme.exe" from its own folder on.my desktop
4) it runs through several windows, tells me it can't find the serial, then the MAC.

I did try inputting my own code for the IMEI, but it then gave me an error saying it couldn't upload. Any help in this matter is greatly appreciated.
 
Last edited:

MaxRabbit

Senior Member
Oct 21, 2010
778
227
Austin
So I'm not sure if I'm doing something wrong here, but for whatever reason !IMEIme cannot recognize my device's serial number. I have tried re-installing drivers, restarting my computer, restarting the kindle, elevating adb first, and nothing seems to be working.

Every time I run the program it says it cannot detect the serial number, nor the MAC address, then it tells me to input an IMEI manually. Judging by the original instructions, it is important that the tool recognizes my device's S/N before continuing. Any advice?

Thanks,

td

Edit: Just for more info, I'm running stock 6.2.1 with root. I tried a big ordeal just now with my drivers to no avail. It seems like the tool is not properly communicating somehow, though adb is certainly communicating fine.

I'm doing these steps:

1) connect kindle
2) select "Disconnect" when the usb transfer option appears on the kindle
3) run "!IMEIme.exe" from its own folder on.my desktop
4) it runs through several windows, tells me it can't find the serial, then the MAC.

I did try inputting my own code for the IMEI, but it then gave me an error saying it couldn't upload. Any help in this matter is greatly appreciated.
It shouldn't be necessary to click "disconnect" on the Kindle. Do you have USB Debugging enabled in the Applications -> Development Settings?

A troubleshooting step: If you run the Kindle Fire Utility with your KF plugged in, does the "ADB Status" and "ADB Rooted" report your Kindle?
 

tduermeier

Senior Member
Oct 8, 2010
81
8
Boulder, CO
It shouldn't be necessary to click "disconnect" on the Kindle. Do you have USB Debugging enabled in the Applications -> Development Settings?

A troubleshooting step: If you run the Kindle Fire Utility with your KF plugged in, does the "ADB Status" and "ADB Rooted" report your Kindle?

So there doesn't appear to be a selection for Development Settings under Applications, all I see when I click on Applications (on the stock rom) is a list of the running applications.

When hooked up to KFU, ADB Status is online, but ADB Rooted says No. My device is running Burritoroot and has SU installed, but if I elevate adb with burritoroot through KFU it will revert back as soon as I close the utility, correct?

Is there anyone who has gotten this to work on a stock, rooted setup that could tell me the steps they followed to make this work?

Regards,

td


Edit:

Tried a couple new things, still to no avail.

1) Ran KFU and elevated adb to have root access, confirmed before and after IMEI through KFU outputting "ADB Rooted: Yes" when prompted to Recheck the device status
2) Did not select "Disconnect" before running utility.

After this attempt I got an error reading:

This will circumvent the intent of this program by using a GENERIC IMEI. This program will not allow this. Program will exit now.

I got this error after selecting "No" to the first prompt regarding a developer's ROM, and "Yes" to the second prompt about In-Place updates. I never saw the "Obtaining IMEI" or "Obtaining Serial Number" or "Obtaining MAC Address" screens at all, this error popped up before any of those screens had a chance.

Then, just to be stubborn, I ran the utility once more and saw it go through a different set of issues, wherein I see "Testing ADB" (no error after this), then the screen flashes to "Obtaining IMEI," which flashes twice, then "Obtaining serial number," which also flashes twice then tells me it could not obtain my serial number, then "Obtaining MAC address," which also flashes twice and tells me it could not obtain it. I am then given a screen where I can input an IMEI base manually and when I hit cancel it gives me the same quoted error above.

It seems like this should be a very simple thing judging by the instructions in the OP, but nothing I've tried has brought me success.
 
Last edited:

ibleo02

Senior Member
Sep 22, 2008
79
11
Texas
No... it won't cause apps to show up that don't show up... BUT

With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.

You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.

You could try the default KF info and if that don't work... make it mimic your Evo

And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.

One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.

Thank you sir, i will try that.
 

tillum

Senior Member
Oct 31, 2009
205
32
I'm running Ubuntu, and having no luck with this method. Could someone point me in the right direction? I've been trying to use this tool under wine, and keep getting the error "Failed to mount ROM to read device information". Adb works under Ubuntu, I can edit files, do everything else, but I can't seem to get this working using this tool under wine. Can you provide me with any ideas on how to fix this? It's crazy that I need to use a Windoze box to fix this.... as android is linux, as is Ubuntu. Cheers.
 

DizzyDen

Senior Member
Feb 7, 2011
1,301
567
So there doesn't appear to be a selection for Development Settings under Applications, all I see when I click on Applications (on the stock rom) is a list of the running applications.

When hooked up to KFU, ADB Status is online, but ADB Rooted says No. My device is running Burritoroot and has SU installed, but if I elevate adb with burritoroot through KFU it will revert back as soon as I close the utility, correct?

Is there anyone who has gotten this to work on a stock, rooted setup that could tell me the steps they followed to make this work?

Regards,

td


Edit:

Tried a couple new things, still to no avail.

1) Ran KFU and elevated adb to have root access, confirmed before and after IMEI through KFU outputting "ADB Rooted: Yes" when prompted to Recheck the device status
2) Did not select "Disconnect" before running utility.

After this attempt I got an error reading:



I got this error after selecting "No" to the first prompt regarding a developer's ROM, and "Yes" to the second prompt about In-Place updates. I never saw the "Obtaining IMEI" or "Obtaining Serial Number" or "Obtaining MAC Address" screens at all, this error popped up before any of those screens had a chance.

Then, just to be stubborn, I ran the utility once more and saw it go through a different set of issues, wherein I see "Testing ADB" (no error after this), then the screen flashes to "Obtaining IMEI," which flashes twice, then "Obtaining serial number," which also flashes twice then tells me it could not obtain my serial number, then "Obtaining MAC address," which also flashes twice and tells me it could not obtain it. I am then given a screen where I can input an IMEI base manually and when I hit cancel it gives me the same quoted error above.

It seems like this should be a very simple thing judging by the instructions in the OP, but nothing I've tried has brought me success.

The error regarding circumventing may be due to the method of rooting used causing your device to report one of the "generic" serial numbers (11223344.... or 12345.... etc) several recovery applications use this and without me taking that into account there could be MANY devices obtaining the same IMEI (which defeats the purpose)... a method you could use is
1. edit !IMEI.ini and set Use_ADB = 0
2. select yes to update developer's ROM
4. manually input your device serial number
5. flash the ROM (the one with -IMEI.zip to the device)

Alternatively you could pull your framework.jar from you /system/framework folder and select no to dev's ROM, and no to inplace... it will then let you browse for your framework file to patch.

I'm running Ubuntu, and having no luck with this method. Could someone point me in the right direction? I've been trying to use this tool under wine, and keep getting the error "Failed to mount ROM to read device information". Adb works under Ubuntu, I can edit files, do everything else, but I can't seem to get this working using this tool under wine. Can you provide me with any ideas on how to fix this? It's crazy that I need to use a Windoze box to fix this.... as android is linux, as is Ubuntu. Cheers.

the "Failed to mount ROM to read device information" shouldn't effect the use on a KF... since the program was originally intended for use on a NookColor... I have it written to mount the ROM partition to read the device specific files... but I also added the use of the "adb getserialno" to obtain device serial number from other devices.
 
Last edited:

tillum

Senior Member
Oct 31, 2009
205
32
I'm confused then, as it doesn't appear to be working... I will check the other error messages I'm getting and post back... basically, the program seems to be quitting with something along the lines of "Unable to generate generic IMEI... quitting" etc. Cheers.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Why do I want this?
    Some apps do not work properly without an IMEI. The example app that I ran into is the XDA free application. Without an IMEI, the XDA app crashes when logging in. I believe it may also affect Terminal Emulator, causing it to force close on launch. The Kindle Fire, at least when running CM7 (not sure about stock), does not have an IMEI built in. Test yours by typing "*#06#" in the dialer.

    Prereq's
    Ensure the Kindle Fire ADB drivers are installed. The Kindle Fire Utility installed them for me.

    Step 1
    Download DizzyDen's IMEI generator.

    Edit .ini to modify build.prop to stock Kindle Fire device identification (optional step)
    (Use if you have issues with the Market or Amazon Appstore allowing you to download apps)
    Settings:
    Device_Manufacturer = TI
    Manufacturer_Device = blaze
    Device_Model = Full Android on Blaze or SDP
    buildpropedits.jpg


    Step 2
    Run the program! For the first option, asking about dev's rom, select "no."
    devornot.jpg


    Choose "yes" for in-place upgrade.
    inplaceupdate.jpg


    It will pop up saying "Failed to read MAC address."

    Ensure that your serial number was found and the IMEI is a correct 00-#### (series of numbers) format.
    imeioutput.jpg


    If all is correct, push to device:
    pushtodevice.jpg


    You must run it again on every ROM update!

    FAQ
    Q: Anything else this program can do?
    A: Look in the !IMEIme.ini file, there are options for spoofing the device manufacturer, etc.
    The following is the relationship from the ini to the build.prop settings:
    Device_Manufacturer edits the ro.product.manufacturer
    Manufacturer_Device edits the ro.product.device
    Device_Model edits the ro.product.model

    Q: Does this program support ICS?
    A: DizzyDen says that it should.

    Q: I've heard messing with IMEIs is illegal.
    A: DizzyDen's program generates an IMEI with a 00- in front, indicating that it is a test IMEI. No illegal spoofing of a real phone is going on.

    Q: Is there any way to add an IMEI to a ROM before flashing?
    A: Yup, just choose "Yes" to "Are you planning to update a dev's ROM zip file?" and choose your ROM.

    Q: Ran it, and under system > About Tablet > IMEI it shows as Unknown.
    A: Normal, test with *#06# in dialer.

    Please consider clicking a "Thanks" to me and to DizzyDen!
    2
    Noobi question guys. Would adding an IMEI allow me to download some market apps that don't otherwise show up? I have a couple of apps that I have on my Evo that I would like to have on my KF. One example is FLCommando. Or is there a different way of doing that?

    No... it won't cause apps to show up that don't show up... BUT

    With the build.prop edits available by simply editing the !IMEI.ini you can get apps to show up.

    You can leave all the information for both devices in the ini file and just place a ; at the beginning of the one you don't want.

    You could try the default KF info and if that don't work... make it mimic your Evo

    And thank you for the write up on the tutorial Max... glad this is getting more info out to other forums other than the NookColor... should work on just about all devices now.

    One thing to be aware of... since the program edits framework.jar for IMEI spoofing... you must run it again on every ROM update.
    1
    Firstly, I've now tried this with both 1.8 & 1.9. After running:
    Code:
    wine imei.exe
    I then choose 'no' for updating a rom, and 'yes' to updating in place. In the terminal I can see that it's recognised the device number in adb, however I am told that: 'This will circumvent the intent of this program by generating a GENERIC IMEI. This program will not allow this. This program will exit now.'

    My device number from 'adb devices' is: 5934000600000001

    It's probably worth noting that I'm starting the adb server as root, as otherwise I can't see my device. I.e., 'sudo ./adb start-server'. After that however, normal adb works fine...
    'adb shell' or 'adb devices', etc. I have been starting adb as root, then trying to run your program.

    I'd love some advice about what to do next. At this point I'd be very happy for a generic framework.jar file I coud push to my device. Any way to generate/edit this? Thanks.

    You can follow the advice regarding setting Use_ADB = 0 and either pulling framework.jar or patching ROM zip file.

    You might also want to try sudo wine imei.exe (I assume you renamed !IMEIMe.exe)
    1
    Thanks so much DizzyDen! Here's my framework.jar file:
    www.curiouslegends.com.au/misc/files/framework.jar

    I'm happy to keep testing this for you to find out what's wrong, so that others can benefit from this. Please let me know if you want me to run any other commands. I'm also going to look at TWRP, which is the recovery I'm using for the kindle fire. Seems like there might be some issue with how they've setup their IMEI in that. Cheers. T

    Just for clarification... recovery will not have an IMEI either... it is how they report the device serial number.

    You can also try issuing the adb getserialno command and see what it reports as the device serial number.

    If I were you I'd also try placing the device serial number in the ini file... one thing about it... I don't know if the ! in the ini filename will cause problems in unix or not... I suspect it might with the issues you had after disabling ADB.

    I am currently looking at methods to use on device realtime IMEI generation as well as porting my program to unix.

    I'll make a couple of modifications to 1.9 and have you test something on your linux machine... namely renaming the ini file and changing the name for it in the program...perhaps that will solve the wine situation.... when I get it done I will post 1.9a in this thread for you to test.

    I attempted to patch it for you, but the program ran and everything was deleted :-/

    I'll get with you and let you know how you have to set up to generate IMEI's that save the patched framework.jar file.

    Edit: the issue above seems to be a bug that has crept in with the addition of some of the newer features... I had to resort to an older version of the IMEI generator to keep from deleting the framework.jar file... I guess I now have more to work on this weekend.
    1
    tillum... I forgot to include the NF device information in the framework.jar... I'll generate a new one with that... that is why the device is not compatible is showing up.

    WOW... can certainly I responded as soon as I rolled out of bed... BC (Before COFFEE)

    To get the other apps to show in market... you will have to edit your build.prop in the /system folder... its NOT in the framework.jar file.

    Additionally, there is currently evidence that market may possibly be using the device fingerprint (ro.build.fingerprint in build.prop) to restrict application availability.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone