yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] deano0714:
Has anyone tried this fix and then used c4droid?... It crashed after trying to run the program.... Ill try this whe I have some free time thanks :)
[Kindle Fire Android Development] tillum:
Firstly, I've now tried this with both 1.8 & 1.9. After running:

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.
[Kindle Fire Android Development] DizzyDen:
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)
[Kindle Fire Android Development] Pkt_Lnt:
Thanks for this! I got a message on first run about faking right after the failed to find MAC address, and it exited. Ran it again and it worked just fine. We will see if it solves my status bar force close.

Sent with Tapatalk / Kindle Fire / CM7 ROM
[Kindle Fire Android Development] tillum:
Still no luck. I have set the imei.ini file (yes, renamed, linux doesn't like the "!" at the front) to disable adb. I even set the wireless and usb options to be disabled, even though the file says this isn't needed. I STILL notice however that in the terminal, when this app is run via wine, that it's starting the adb server, and trying to find the device.

I have tried now both patching the framework.jar file on it's own, and patching the 7.1.0 cyanogenmod rom for the kindle fire, both with no success. Each time I'm met with the same error as before: 'This will circumvent the intent of this program by generating a GENERIC IMEI. This program will now exit.'

I have also tried running wine as root... i.e., "sudo wine IMEA.exe" (yes, again, I renamed the .exe file) Same error as above. Seems to be trying to start the adb server. Makes no difference if there's nothing there, i.e., no usb cable plugged in, or the server started beforehand.

Am I able to just get someone to send me a generic IMEI that I can use, and just push to my device? Ta.
[Kindle Fire Android Development] DizzyDen:
tillum, pull your framework.jar file and post it somewhere for me to download and I'll patch it with an IMEI based by using your username here for the seed.
[Kindle Fire Android Development] tillum:
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
[Kindle Fire Android Development] MaxRabbit:
I attempted to patch it for you, but the program ran and everything was deleted :-/
[Kindle Fire Android Development] DizzyDen:
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'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.
[Kindle Fire Android Development] tillum:
Great! Thanks for that DizzyDen, I look forward to having something to test. Will have a try later with the serial number and see how it works. For the record I've been using 1.8, which has an .ini file I can edit when I extract the .zip. There is no .ini file with 1.9 on extraction. Cheers.
[Kindle Fire Android Development] DizzyDen:
OK... 1.8 is not going to work on your KF... that is specifically why I came out with 1.9.... you can use the same ini from 1.8.... the files are compiled into the exe so running 1.9 should have created the ini the first time it was ran... with the default settings... it can be edited after that.

I included the ini file in the zip of 1.8 due to additional settings I wanted people to be able to edit prior to running it... sorry about the confusion on that.
[Kindle Fire Android Development] tillum:
Right. In that case, I'll have a play with 1.9 and see what I come up with.

T
[Kindle Fire Android Development] tillum:
Firstly, I tried running the 1.9 .exe file without changing the name, simply by right clicking and choosing 'run with wine'. Not as good as the terminal perhaps, but easy to get around the "!" at the start of the file name thia way. Harder to debug though...

Anyway, same issue as before, in that the program stopped by saying it couldn't generate a generic IMEI. So I opened up the .ini file that was generated, filled in the details of my device from the front page of this thread (this was minus my device number), turned off adb, and ran it again. Same problem, only this time after choosing 'no' with patching a rom, I wasn't given another option. Stopped with the same mesage though... can't generate a generic IMEI... etc.

I have just pushed the framework.jar file that DizzyDen left for me to my device. (thanks!) I renamed the old one, then updated the permissions, etc, of the new file. After rebooting, have found that there's no differene with the market... still am told with various apps that my device is not compatible.... frustrating. So I have just now wiped all the settings under market in my applications section, and rebooted. No change. Still hit with my device is not compatible...

Using the app 'Show Me My IMEI', I now seem to have an IMEI number, starting with "00". So... I am wondering now even if I do actually get this program working, if there's any chance this will improve this outcome... So perhaps it's possible that there are a couple apps out there that disable installation on a device with a 'test' IMEI number...hmmmm....

I'm open to other suggestions, and I'll try your suggestion DizzyDen about manually entering the device serial number, and keep trying to see what this takes to get this device working as is. Cheers.

Edit: Ok, thanks to DizzyDen I have an IMEI number now. Thanks mate! XDA app works perfectly now, amongst other things. Will keep playing around with the other files. What other reasons besides the IMEI issue would a market app have for refusing to install? Thanks. T
[Kindle Fire Android Development] DizzyDen:
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.
[Kindle Fire Android Development] BugsyM:
Have the people that are posting that everything went successful been able to access "Kindle Edition" apps in the Amazon App market?

I bought a bunch of the kindle edition games, and would like to continue to purchase them, so I've been trying to get it working on CM7.

After I went through this guide successfully, I still couldn't get them to work. One thing came to another, and I've changed most things in my build.prop back to stock and am still unable to access them.

However I do see 5 new "TI Full Android on Blaze or SDP" devices in my Amazon "Devices" list, so it must be looking at the build.prop, seeing either A. somethings changed or B. it's not the same build.prop file, and deciding I'm not worthy of Kindle Edition goodness.

I'm wondering if the "serial number" thats prominently displayed when you click "manage" on your original Kindle device on the list is what's holding me up?

Edit: I know this may be counter-intuitive to what most people are looking for(wider google market access), but I gotta try somewhere right? :)
[Kindle Fire Android Development] tillum:
Wow... that's dedication! Am replying to this post morning coffee. I'm well and truly addicted at this point. Thanks so much for being willing to recreate this file for me, I really appreciate it! Will keep going later on to try and do this myself, will have to wait till tonight (morning as I write now). I'm familiar with the build.prop file, but where do I find information about editing it for access to the marketplace ? cheers. T
[Kindle Fire Android Development] tduermeier:
So I got a bit fed up trying to make this work on my personal KF and just paid the .99 for the premium app. Working great. Thanks for the help along the way to everyone!
[Kindle Fire Android Development] DizzyDen:
IMEI Gen 1.9a

For those using Unix based systems... you may want to give this one a shot and let me know if it works better... The only difference in this and version 1.9 is the name of the exe and ini files... the other bugs I noticed in 1.9 regarding cleaning up and deleting files when it shouldn't still exist.

Note that this one is only for testing at this point... doesn't have my icon... but identical from released versions other than these items.

Also note... a fellow Nooker has teamed up with me and we are working toward an on-device bash script for this... more on that as we progress.

Ultimately I would love to have my patch to framework.jar read the information from the device and return the imei itself... without having to patch the imei into it.
[Kindle Fire Android Development] tillum:
Awesome. Will have a play and let you know how I go. T
[Kindle Fire Android Development] DizzyDen:
waiting for information regarding 1.9a before I go forward...
[Kindle Fire Android Development] DizzyDen:
The adb in the program is the same as the standard adb.exe from the sdk... you might want to try sudo adb.exe devices to see if that does anything for the problem.

Did you by chance try sudo wine IMEI.exe (shouldn't have had to change name in 1.9a.. i removed the ! from the filenames) to see if that would work?

You may also need to check the version of java you're running and note the versions in the linked thread in the OP

In the works is the on device and a unix port of the generator.

To edit the build.prop file just use the adb you have working to pull /system/build.prop and edit the file as you want. Then adb remount to make the /system partition r/w and push the file back... you might have to change permissions on it... but I never have had to.
[Kindle Fire Android Development] tillum:
Yep, no difference, whether I used sudo on wine or not. Also, I can't run sudo adb.exe as its through wine, so sudo wine adb.exe

Again, tried it, no difference. Next step will be trying this under windows in virtualbox. Any headway on something mote native? (Either android or desktop Linux)

Also, you mentioned there wad some problem with the framework.jar file you sent me, and that because of this it wouldn't fix the market problem (what's not related to the build.prop anyway) . Are you able to send through an updated version? Thanks again for your support. T
[Kindle Fire Android Development] Elbob10s:
Had to run it twice for it to work for me. First time after it rebooted I still had no IMEI but the build.prop changes were in effect.
[Kindle Fire Android Development] Vashypooh:
Ran it, and under system > About Tablet > IMEI it shows as Unknown.

This how it should look?
[Kindle Fire Android Development] DizzyDen:
The framework.jar I sent is actually fine... That was my before coffee error... the market issues you see are due to build.prop... not framework.jar

That is normal... it is a ROM issue... if you're using CM7 you can dial *#06# in the phone app... or use an IMEI app from market... they will both return your generated IMEI properly.
[Kindle Fire Android Development] tillum:
Thanks. Looks like I may not be able to resolve the market issue fully... have an edited build.prop, but the curreny "fix" for the market involves using an older version... which misses many of the more recent apps. So for now, I'll try side loading apps I need from my phone. The IMEI fix works great for the XDA app though, amongst others.

Let me know when you have a more native solution for IMEI generation to test. T

Sent via Fire
[Kindle Fire Android Development] gunza:
hulu

I just want to point out that if you do this, you will lose access to hulu plus on your device. Hulu must check the IMEI to determine if you are "supported", and if you arent one of their accepted IMEI's, it blocks you. There is a thread with a modded hulu plus apk to get around this:

http://xdaforums.com/showthread.php?t=1449110

However, neither of these versions are really optimized for the tablet.

-gunza
[Kindle Fire Android Development] DizzyDen:
One thing... note the comment I made in an earlier post regarding build.prop edits... it seems now you not only have to edit Manufacturer, Device, and Product but also the fingerprint.

The native solutions are still in the works and I will let you know when I'm comfortable with something for others to test.

Unless Hulu has made very recent changes... there is no check against "valid" or "supported" IMEI's... they were only checking the existance of an IMEI. That is actually one of the programs that prompted the IMEI generator in the first place.
[Kindle Fire Android Development] chairshot215:
Has anyone used Auto-Killer after running this utility? Based on the apps I use I find lowering the value for hidden apps and then splitting the difference of what was subtracted by raising Content and Empty apps keeps more of the apps I would prefer be running from being killed by the OS. Anyhow I ran the app fine on stock but get nothing but Force Closes on CM7. Otherwise I am apparently not running any apps that require an IMEI, thanks.
[Kindle Fire Android Development] huchman:
Just want standard fire apps

Is there an easy way to make this look like a standard Kindle Fire to the Amazon app market? I figured it would be a simple build prop edit.

If it matters I am using bare bones CM7. Thanks
[Kindle Fire Android Development] dnathan13:
I cant get xda free to work on ICS. It was working before on cm7 using this, but now I can use the app until I log in then it force closes when I try to open any threads. Rerunning this does not fix it either. Any thoughts?
[Kindle Fire Android Development] jfb9301:
I've had about the same results with ICS. With or without the IMEI fix. I tried mentioning this in the ICS thread, but was generally ignored. You could give it a shot though. Maybe more people with the problem will raise attention to it.
[Kindle Fire Android Development] ProfEngr:
Will this work for the Galaxy Tab 10.1 wifi-only? If so, what info should I put in the ini?
[Kindle Fire Android Development] DizzyDen:
It should work with the default ini settings... It will most likely NOT be able to read the serial number or MAC address so you will have to specify an IMEI seed... you may want to put that seed in the ini... ProfEngr would be a good seed ;)
[Kindle Fire Android Development] blkdimnd:
Generic MEI???

I can't seem to get this to work on my rooted Kindle Fire.

The interface is completely different (IMEIme 2.0) and I am not able to select any options.

Also, when I run the program I must mod the ROM, which is fine, but once completed the program says it can not generate a Generic MEI.

Is there something I'm missing here?

I'd like to use this so I can get Sirius working on my Kindle

I'm currently running:

[ROM] 11 Apr Gr8 (6.3) - MoDaCo Custom ROM for the Kindle Fire

[RECOVERY] TeamWin Recovery Project (twrp) 2.1.0

[BOOT] FIREFIREFIRE 1.2
[Kindle Fire Android Development] DizzyDen:
2.0a bug fix uploaded... thanks for the bug report.
[Kindle Fire Android Development] Bigboij:
anyone got a guide for this new 2.0 gui cant figure this out to get it to pull my serial
[Kindle Fire Android Development] DizzyDen:
If you used it before... use the same ini settings you did. The GUI will read your ini settings and set the options accordingly.
[Kindle Fire Android Development] Bigboij:
first time doing this do i need to manually pull my serial and input it? what would be the correct formatting
[Kindle Fire Android Development] DizzyDen:
If you have ADB working on your computer to your nook... it is simple...

1. Update options:

Update Device

Check ADB(usb) and/or ADB(WiFi) (if you are using adb wifi version on your device)

2. IMEI Generation Options:

Select Serial Number

17 Digit

Encrypt is whatever your preference is

3.Build Prop [system/build.prop] Edit:

Build Prop Edits

Device Information and select Kindle Fire device

LCD Density is your preference

4. Misc. Options:

Cleanup when exiting

Save Settings

When you click Generate it will save those settings in the ini file and read them in next time.... It will then try to communicate with your device and pull its serial number for use in IMEI generation....

If it gives you an error about trying to generate a generic imei... post back and let me know... but you can just put your serial number in the IMEI_or_SEED box just like it is.
[Kindle Fire Android Development] blkdimnd:
GUI Issues

The new GUI still doesn't work for me. I can't change and of the default options.

But I can edit the .ini manual and then run the program.
[Kindle Fire Android Development] DizzyDen:
Are you using 2.0 or 2.0a? This was an issue with 2.0 (I built the wrong version) but should be fixed with 2.0a
[Kindle Fire Android Development] blkdimnd:
I'm an idiot...I was still using 2.0.

Even-thou I downloaded 2.0a.

2.0a is working great!

Thanks for the help and making this great program.
[Kindle Fire Android Development] Bigboij:
looks like that worked thanks for the instruction, its rebooting now... came back up but shows IMEI unknown in status on the kindle... it looks like the process when through correctly.

tried it again got the same successful per app message, reboot no IMEI still unknown
[Kindle Fire Android Development] DizzyDen:
No worries... I just wanted to verify since I was pretty sure I hadn't messed up the upload again... glad its working.

This is quite normal... if your device has phone apps you may try dialing *#06# and see if an IMEI is reported... or download an IMEI reporting app from market and it'll show you do have one.
[Kindle Fire Android Development] Bigboij:
got an app and it shows up, now listening to xm :)
[Kindle Fire Android Development] DizzyDen:
With the new update (IMEIme 2.1.0.3) it will now show in about tablet - status - IMEI and IMEI SV
[Kindle Fire Android Development] dbramage:
Guide?

Hey i like the idea, but ive tried a handful of times/configurations and nothing changes in any of the markets. what am i doing wrong. Its a little hard to tell cause your app has been updated since you wrote the guide instructions. Please help. :laugh:
[Kindle Fire Android Development] M3wThr33:
I'm not having any luck with the Gr9 (6.3.1) - MoDaCo Custom ROM.

I noticed over USB it doesn't see the device using the provided adb, but the installed one works fine.

Over Wifi adb I have no luck, either.

Running it directly from the android sdk folder will see the serial (no MAC as expected) and generate an IMEI, but any app I run won't see it, even though it said success.

Also, at least from ES File Explorer, there's no /efs folder.
[Kindle Fire Android Development] DizzyDen:
What version of IMEIme are you using? It doesn't make sense why the included adb.exe wouldn't work... it is the one from the sdk... however, if you are running the newest version of IMEIme, it doesn't have to communicate with the device if you base the IMEI off of the serial number.

As far as the /efs folder... I can't tell you about that... the IMEI Generator does not even look for that folder... much less modify anything in it.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Just saw this today...

http://www.engadget.com/2012/01/09/...kyrocket-hd-coming-to-atandt-1-5ghz-dual-cor/

I think I may make the switch if it is half as good as I hope. Hopefully they learned from their flaws with the skyrocket.
[AT&T Samsung Galaxy S II SGH-I777] jdbeitz:
Nope. I'm staying put with the sgsII!

Sent from my AT&T cellular device.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Just curious as to what makes you say that? No interest in the LTE, bigger screen or new form factor?
[AT&T Samsung Galaxy S II SGH-I777] Red5:
Depends on what the Processor is and what OS version it will come with.
[AT&T Samsung Galaxy S II SGH-I777] honghsien5:
i'm actually quite interested in the new skyrocket HD.

However, since there's SGS2 and skyrocket on the market for AT&T already, i doubt that many developers would make the jump and support skyrocket HD.

so i'm just gonna stick with my i777 because i love the developers here
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Even if i could, no for the sole reason that it's most likely got a snapdragon chip
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
That too is a huge fear I have and is really my only major drawback to the device.
[AT&T Samsung Galaxy S II SGH-I777] cfaberlle:
Now that Orlando will have LTE this is very tempting, but then again I am having way too much fun with the SGS2 to even think about replacing it. :D

Maybe if they announce it will have the dual core 1.5ghz exynos processors I'll give it another thought.
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Samsung is going overboard. They should have released one galaxy s2 with their lte exynos and have a super amoled plus HD, THAT'S innovation, this is BS and gives Android a bad name for fragmentation
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Isn't the GSIII also set to release this spring/summer as well lol?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
If it's Crapdragon - hell no.

If it's Exynos - tempting, but I've already purchased one out-of-cycle upgrade, don't need the extra 300 MHz, and LTE will be worthless for at least 2-3 more years here.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
2-3 years? How do you figure that?
[AT&T Samsung Galaxy S II SGH-I777] Boobie Watcher:
I get an upgrade once a year with at&t, I got the gs2 the day it came out....so i still have about 7months left untill I can get my upgrade, by that time something bigger and better will be around....if not, i will for sure look into this phone.