yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] DizzyDen:
You can use any device you want... I use GalaxyS because I have that phone and it works to fix the limited Market we had (and may still have without edits).

The build.prop edits only effect market (now Play Store) app availibility.

You could use Kindle Fire, Nook Tablet, Galaxy S2, HP Touchpad... or any device you want, as long as you have the info needed to match:

ro.product.manufacturer

ro.product.device

ro.product.model
[Nook Color Android Development] Miltani:
after editing my build.prop file im still unable to see gameloft games for the nook :(
[Nook Color Android Development] DizzyDen:
Try the edits in this thread.
[Nook Color Android Development] otaku91:
DizzyDen: thanks for the work on this. It's really appreciated. I have one quick question. Does the program work on the ICS builds? I have one app, RockPlayer, tied to the IMEI that I use quite a bit. That has kept me from really considering an ICS ROM.
[Nook Color Android Development] DizzyDen:
One thing that does not work with ICS is changing display density... it will cause issues. I am going to update the generator to solve this.

EDIT: The Generator will not cause an issue with ICS... since it will not find a density line in build.prop... it will not change it ;)

Other than that... it will work for ICS.
[Nook Color Android Development] DizzyDen:
Teaser alert

Just lettin ya all in on what I'm workin on for the IMEI Generator...

Attached is a screen capture of the new interface... any input would be appreciated at this point... If you can't post in this thread... then use the BUG REPORTING thread... I'll be keeping a close eye on both as I continue developing the newest update.

If anyone has any idea how to get an installable zip file to mount /data to install local.prop I'd incorporate build.prop edits to that file for better ICS compatibility... however keep in mind... it has to work regardless of EMMC or uSD installs...

In the meantime... back to completing the interface to program functionality.
[Nook Color Android Development] MaxRabbit:
Pretty!

10char
[Nook Color Android Development] baldbear:
This does not work for an Acer Iconia a500 on the 3.2 version of android, it fails when trying to extract the framework.jar file

But,

I did get it to work on a MotoACTV sports watch! I now have Sirius XM on a tiny, tiny device!
[Nook Color Android Development] towir022:
Will this work on a 16GB nook tablet running CM7 ?
[Nook Color Android Development] DizzyDen:
Version 2.0 with new GUI uploaded

New version uploaded... new GUI... OP updated.
[Nook Color Android Development] DizzyDen:
If you can provide the framework.jar file... pehaps I can figure out why its not working... if you mean extracting framework.jar from the ROM zip file... probably corrupt download.

I don't know... I don't have one to test on... you can try it and report back ;)
[Nook Color Android Development] blkdimnd:
Kindle Fire??

I have posted this also here:

**Clicky**

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

I am not able to select any options in the new interface.

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
[Nook Color Android Development] DizzyDen:
Thanks for the report... 2.0a uploaded.
[Nook Color Android Development] hector12t:
I am having this issue as well. I am using the 2.0a
[Nook Color Android Development] DizzyDen:
That is with the device connected? has adb worked for you in the past?
[Nook Color Android Development] hector12t:
yes and yes
[Nook Color Android Development] DizzyDen:
First... try going to command prompt and typing in:

java -version

make sure it is above 1.6.0_23 (per OP in CAVEATS)

If that is above that version... and in your path... try typing:

adb get-serialno

this should verify adb working and communicating with device... if that fails then the program cannot communicate with the device... you can either use ADB WIRELESS from play store... or manually input serial number or IMEI seed.
[Nook Color Android Development] gallahad2000:
I keep getting the "Generic IMEI" error when trying to update a Mirage-CM7.2.zip even after putting my serial in as the Seed. I also tried ADB over wifi and got the same error. I tried to put my seed into the !IMEI.ini like I used to on previous versions and that also results in the error. Trying to apply the patch after flashing results in the same error.

I just double checked my adb over wifi and it reports that it's connected.

I've also tried using the MAC address which also gives error.

adb get-serialno just gives me the IP address of adb over wifi

java version is 1.6.0_24

*#06# gives a blank IMEI
[Nook Color Android Development] DizzyDen:
Please make sure you are using 2.0a

In the meantime I will look into it deeper... but do not see where the addition of the GUI would cause this.
[Nook Color Android Development] pspunderground:
Can we get an older version posted up?
[Nook Color Android Development] DizzyDen:
I've done this in the past... but have found that people wind up just using the old one and I get no feedback on the newer.

My preference is to get the new version fixed... the more versions I have up... the more I have to support.

I don't think anyone could complain about how quickly I respond to bug reports or the speed in fixing them.

I'll be on IRC tonight if anyone wants to stop by and help troubleshoot this generice imei circumvent issue. I cannot duplicate it, nor do I see where in the code it could be caused.

gallahad or hector or anyone else with the generic IMEI issue... can you check the bottom of your ini file and see if Use_Serial_Number is set to True... not 1, but the word True.... if so, I think I found the problem... waiting to update 2.0b until someone reports back.

NM... uploading 2.0b now.... I'm sure people will let me know if its fixed or not.
[Nook Color Android Development] racks11479:
Yo Dizzy!

Saw your post on my thread and wanted to make sure you get my reply so I"m hijacking your thread and posting my reply here :P.

But if you could add the option to prep any .zips to flash for my dualbootsd that would be awesome!! Let me know if you wanna go ahead and do it and if you need anything from me. :D

Thanks,

Racks
[Nook Color Android Development] gallahad2000:
Getting the generic error with 2.0b

It doesn't work for updating a rom from a seed. (Settings used are attached).

*Also does not work using adb over wifi.

*Grabbing Phiremod now in case this error is specific to the Mirage KANG.

*Phiremod pulling serial using adb over wifi also fails

Use_serial_number is set to 1, not True.

****Randomly hitting buttons, I think I may have found the problem: "Use Previous Fix", if this is clicked it will return the generic error and it is clicked by default.

****Unclicking "Use Previous Fix" works for both adb over wifi and typing in the seed.
[Nook Color Android Development] DizzyDen:
OK... thanks for you delving deeper... I will look into why Use Previous Fix is failing... I am assuming you don't have the imei.fix file in the folder... will have to make it not think generic if that's the case...

Should have 2.1 up sometime this evening with that fixed... but the include custom patches will probably wait for 2.2 now ;)

If you do have an imei.fix file... could check one more thing I'd appreciate it.... what does your imei.fix file have for the IMEI on line 8?
[Nook Color Android Development] gallahad2000:
No problem, thank you for your continued work on this project.

I don't have an imei.fix file and don't know how to generate one.

Thoughts:

I'm not sure what a lot of the buttons are for. I feel like I'm a fairly competent andro-phile but I don't know whether to use a 15 digit, 17 digit, encrypt, etc. I also wasn't sure what the build.prop edit button did until I read the IMEI.ini. It might make more sense to just have the device info and lcd buttons without another "master switch."

Also, I've noticed with this last install that the build.prop edits require more changes than they used to. I think google has noticed modders altering the build.prop and now check more locations for compatibility. I'll have to test compatibility with this app's patch tonight when I flash the rom but when I manually made the standard changes a few days ago the market was still blocking a lot of apps.
[Nook Color Android Development] DizzyDen:
I understand where you're coming from... perhaps a little insight to my thinking will help... and rememer... I earned the Dizzy part of the nic ;)

Use 15 or Use 17... does not matter at this point... I intend to include the calculation routine to be able to use 15 digit IMEI... the option has always been there in the ini... but is ignored as of now... it always generates 17 digit IMEI's... so either radio works the same (for now).

The encrypt IMEI check is for the conspiracy theorists who do not want 15 digits of their Serial Number or MAC address being used in its "raw" form... the program will use an internal encryption to the information to create its own unique number from the information.

The "master switch" for build.prop edits... I thought about this one a LOT... it is a quick easy way to disable build.prop edits (only one button to uncheck to disable)... may change my mind on this if enough want me to do away with it.

The new use of the devices.dat file should aid in the additional build.prop edits needed. I include ro.build.fingerprint now as well.

When I started working hot and heavy on the GUI I create a thread for input for device information and asked for input to the GUI itself... When I didn't receive opnions, I just went forward from what I had in the ini file and what device information I had available.

BTW... if you have your previous ini file... the program will read the settings in it and use them...

All of the options should also have a mouse-over pop up explaining the setting as well...

Also... the Hybrid is non-functional at this point... another down the road intent... it will work the same as the program did with both Serial Number and MAC address set to 1 in the ini file and will base the IMEI off of the Serial Number.
[Nook Color Android Development] otaku91:
Quick Question, will choosing the Kindle Fire Option in the build.prop edits allow me to install Kindle Fire Edition apps in the Amazon App Store?
[Nook Color Android Development] DizzyDen:
I don't know... you could give them a shot... don't know if they will work on our hardware or not... onlyl put that in because some people using Kindle Fire use the IMEI Generator.
[Nook Color Android Development] vesponauta:
I have a newbee question :) When i'm trying to generate a new imei i have a result like this 00-5684-5214-698 etc.

Can i eliminate the - from the imei?
[Nook Color Android Development] DizzyDen:
While there are no signs of strict enforcement of the standards when it comes to use of IMEI's, I have chosen to have the program adhere to those standards.
[Nook Color Android Development] vesponauta:
so now, i can't recover my imei to the original??
[Nook Color Android Development] DizzyDen:
The Nook Color never had an original IMEI... that's why this program was created....

You can flash a non-IMEI generated flash.
[Nook Color Android Development] luci5r69:
Guys,

I'm sorry to be a n00b here but I'm having a slightly hard time understanding how exactly to use this application.

I have a Nook Color (1.4.2) and I've used Verygreen's CM7 on SD Card method to run CM7 on my NC. Everything's running great -- no problems. However, I simply want to make the NC appear as a "Samsung Galaxy Tab" to the market, and I believe I can do that using this app, I just don't know how.

Can anyone guide me?

Thanks!!
[Nook Color Android Development] DizzyDen:
The generator is still going to patch framework.jar with an IMEI... no problem there at all... what you need to do is run the generator...

1. Select if you want to update ROM for flashing to device or want to Update Device (in-place update)

2. If you are going to use device for IMEI (recommended) OR are going to use in-place update... check either ADB(usb) or ADB(WiFi) or both...

3. Select whether to base generated IMEI off of Serial Number or MAC Address...

4. IF you are a conspiracy theorist... check Encrypt IMEI

5. you can enter NOOK's serial number where it says IMEI_or_SEED if you want... or if you are not pulling the info from the device via ADB...

6. make sure Build Prop Edits is checked...

7. make sure Device Informatino is checked... Select either DizzyDen's Settings (Samsung GalaxyS phone) or Samsung Galaxy Tab from the drop down list of devices...

8. if you want to change the LCD Density... check it and select LCD Density you want (you can also type in a Density if you want non-standard)

That is all you NEED... but I recommend checking Cleanup when exiting and Save Changes.

Checking Use Previous Fix will assist in not having to pull information from the device on future runs of the program... since it will save the generated imei.fix file for patching framework.jar on future updates.

Hopefully this information helps you out... btw... all of the radio buttons, check boxes and entry . drop down combo boxes have mouse over infromation explaining what the option is for.
[Nook Color Android Development] luci5r69:
THANK YOU!! Thank you so much for such a detailed explanation. I was trying to understand everything using the explanatory mouse-hovers on each time but I was still failing and I think primarily I didn't want to just go ahead and do something and figure out later if I screwed something up or not.

LOL about the 'Conspiracy Theorist' comment. I'll leave that one unchecked; I'm one of those who does believe we landed on the moon ... LOL.

I've understood all settings well now and I'll use the Samsung Galaxy Tab option; I only have one question. The LCD Density ... I don't quite understand that one, I'm not sure what it does and more important, in my case, if I should change it and if so, to what.

Thanks!!
[Nook Color Android Development] DizzyDen:
LCD Density is like changing the density on your computer... except it is backwards... higher number will cause icons and eveything be bigger.

NookColor stock =169.33333

CM7 CM9 = 160

Phone GUI generally = 240

Some people like larger layout and text with CM* and will select 240
[Nook Color Android Development] luci5r69:
Thanks for the explanation; I was able to look up information similar to that and proceeded with the "160" option for the LCD Density.

So I just used the Generator and everything went very well; I can see now that on the Market the phone is appearing as an "SPH-P100" instead of "B&N Nook Color" ... so your Generator definitely did the trick and works excellent. Thank you so much for such a wonderful program.

Unfortunately, I'm still back on Square One with the issue for which I started this whole shenanigan. Although my NC is now appearing as a Samsung Galaxy Tab (Thanks to your program), the Apps that were coming up as "Incompatible" before are still coming up as "Incompatible" now with the SPH-P100. I'm not sure why.

Take a look at this:

Is this normal? So you really can't install some apps for an android tablet on the NC even if it appears as the Samsung Galaxy Tab? Should I be using some other option (besides Samsung Galaxy Tab) to be able to install these apps?

Thanks again; I appreciate it.
[Nook Color Android Development] DizzyDen:
Did you go in and clear data/cache on google's applications?
[Nook Color Android Development] luci5r69:
Dizzy ... I have a Google Application Framework and a Google Play Store in the Manage Applications area; do I need to Clear Data & Clear Cache on both of them?

Thanks!
[Nook Color Android Development] DizzyDen:
Yeah... Clear on both... clearing Data also clears cache if I remember correctly.
[Nook Color Android Development] luci5r69:
Tried that, but it didn't change anything. But I'll try what you suggested in one of my other threads. Thanks.
[Nook Color Android Development] drmxmyt:
I have a weird issue. im using nook simple touch. tried that tool at first time via adb wireless, seemed like working, device reset etc, but imei wasnt fixed, it was changing constantly. i tried to run it again, and this time said: this device already has an imei, and will use that.. anyway, finished, rebooted but nothing happened again, my imei was changing constantly.(i was checking it with show me my imei). whatever i did, didnt worked.

then i formatted my device, and tried again, it kept saying this device already has imei, will use that(even after format? how can it be possible?).. i checked the crc of the file before and after the use of program and they are same, so program doesnt change my framework.jar at all.

i decided to use an install zip. copied my framework.jar into it, opened the program. it finished and i checked the crcs of framework.jar`s again, it was the same. somehow the program keep saying the device already has an imei, and doesnt change my framework.jar no matter what i do.

i also coppied the jars from my few months old backups and tried with that jars too. didnt worked. now show me my imei shows me a blank line..

(i did several chace and dalvik-chace cleanups, and also used imei generator with almost all settings in that proccess..)
[Nook Color Android Development] DizzyDen:
The reason the IMEI Generator tells you the device already has an IMEI is that it puts a file on /rom called imei and uses the value from that.

First thing I'd check is the version of java on your machine.

Does the IMEI generator show your serial number and MAC address?

EDIT I have no idea why the IMEI would be "changing constantly" since the method currently used patches the IMEI directly into the framework.jar in /android/telephony/TelephonyManager.smali

There will be an update soon that no longer patches the IMEI hardcoded this way... when using Serial Number and not encrypting at least... the patches when using raw serial number will be:

# /com/android/internal/telephony/gsm/GSMPhone.smali
# rename current getDeviceId() to getDeviceId2() then paste this at the end
#

.method public getDeviceId()Ljava/lang/String;
.registers 5

.prologue
sget-object v1, Landroid/os/Build;->SERIAL:Ljava/lang/String;

.local v1, str:Ljava/lang/String;
new-instance v0, Ljava/lang/StringBuffer;

const/4 v2, 0x1

invoke-virtual {v1, v2}, Ljava/lang/String;->substring(I)Ljava/lang/String;
move-result-object v2

invoke-direct {v0, v2}, Ljava/lang/StringBuffer;-><init>(Ljava/lang/String;)V

.local v0, sb:Ljava/lang/StringBuffer;
const/4 v2, 0x0
const-string v3, "00-"

invoke-virtual {v0, v2, v3}, Ljava/lang/StringBuffer;->insert(ILjava/lang/String;)Ljava/lang/StringBuffer;

const/16 v2, 0x9
const-string v3, "-"

invoke-virtual {v0, v2, v3}, Ljava/lang/StringBuffer;->insert(ILjava/lang/String;)Ljava/lang/StringBuffer;

const/16 v2, 0x10
const-string v3, "-"

invoke-virtual {v0, v2, v3}, Ljava/lang/StringBuffer;->insert(ILjava/lang/String;)Ljava/lang/StringBuffer;

invoke-virtual {v0}, Ljava/lang/StringBuffer;->toString()Ljava/lang/String;

move-result-object v1

return-object v1
.end method

This will result in anything calling GetDeviceID() to return the first 15 digits of your Serial Number formatted as a test pattern IMEI and not having to hard code the IMEI into framework.jar

Thanks a ton to HacDan on IRC for this... I finally got it working for other ROMs after you got it on CM9... I knew if it worked in there.. I could get it working on others

EDIT2: did you use PDroid or something else that generates random IMEIs?
[Nook Color Android Development] drmxmyt:
i didnt use anything about imei so far. imei generator shows my mac and serial right. i also checked my /rom path and yes there is an imei file, i deleted it from there and will try to patch my jar again.

edit. didnt work again.

also now im sure that it doesnt change my jar at all. at least this time didnt say `this device already has an imei`..
[Nook Color Android Development] DizzyDen:
Are you pulling framework from your device via in place update... or extracting it from a rom... or browsing to an existing framework.jar?

Not having a nook touch... it is hard for me to tell you what the problem is... but I could download a rom for nook touch and verify the generator works against it.

EDIT B&N certainly did something in the zip files for Nook Touch... I cannot even manually update the framework.jar using winrar... I assume they made their zip files protected. The best you'll be able to do is use in-place updating (Update Device selected)

BTW... you should have seen the error message about the rom couldn't be updated due to duplicate files (this is actually erronious in this situation)... error messages are pretty important to include.

I will have an update very soon that will correct keeping framework.jar on the error.
[Nook Color Android Development] drmxmyt:
i tried to do both. inplace update and rom update. b&n`s update didnt work indeed, so i did a cwm update zip myself, just put framework.jar to system/framework/ in zip and it supposed to change the jar right? it didnt. when its in progress, i may able to copy TelephonyManager.smali and opened, its edited

i think the problem occurs when its compressing classes.dex.

compared the update zips crcs and they are different but jar`s ones are the same. also a guy told he could able to make it work which is weird.

http://xdaforums.com/showpost.php?p=28482260&postcount=6
[Nook Color Android Development] DizzyDen:
Try this test version... it will still give you the errors on B&N's rom from the site... but it will not delete the recompiled framework.jar... and it definately has been changing the framework.jar... it grows by 14KB... which is correct.

EDIT: I assume this worked... since I haven't heard any more about this.
[Nook Color Android Development] drmxmyt:
it didnt work either, sent you a pm.
[Nook Color Android Development] DizzyDen:
Try to run the generator on the zip file... it will still fail... BUT it will keep the imei'd framework.jar in the same folder as the update.zip