yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] 12paq:
Nice!

Always look forward to your updates. Thanks.

I'd be happy to test the app and pull logs for you, when and if needed.

.
[Nook Color Android Development] quepaso:
Just installed it, and i used settings you used. Now when using the new market, its still the same thing, Quickpic still doesnt load up as installable. I checked buildprop with root explorer and it has all the proper info uptop. Samsung ontop row, then 2nd row is GalaxyS, then third row is SCH-I500
[Nook Color Android Development] DizzyDen:
I don't know... I just checked quickpic and it had an update... with update button available... it updated just fine... using the manufacturer information I provided:

ini settings:

Device_Manufacturer = Samsung

Manufacturer_Device = GalaxyS

Device_Model = SCH-I500
[Nook Color Android Development] quepaso:
If you have the app side loaded or previously installed, you can open/uninstall/update it just fine, just not possible if its done normally within the new market. Anyway, i removed the updates for market and old market showed up and i could install anything i needed just fine. I wish we could make it so it just will not use the new market period.
[Nook Color Android Development] DizzyDen:
QuicPic was not side loaded. It was installed from market some time ago.

Always remember...

YCGIYWG

(You Can't Get... If You Won't Give)
[Nook Color Android Development] topcaser:
Hi Dizzy,

i flashed latest nightly 155 and unfortunately running your 1.6 dont pushes the right framework.jar (at least it seems that it is not pushed - actually iam not sure). I get an error message at the end of using your little tool: It seems we have problems to reboot .... or something like that.

I just used all the defaults of your program - did not modified anything. I tried it via adb wireless (it worked in previous versions with previous nightlies very well out of the box).

I saw the file explorer in the background and realized that framework.jar was pulled correct from the device. Also the telephony.smali (dont know the exact name) which was a problem in previous verisons was there.

So, what do you recommend to me?
[Nook Color Android Development] DizzyDen:
Top... I'd try to see if it actually assigned the IMEI and just gave an eronious error message. If it can't create and pull framework.jar.bak it is going to give the error. Use CM7's phone app and dial *#06# and see if it gives you an IMEI.

BTW sorry it took so long to reply... my ISP got hit by lightning so I was waitiny til I got to work... but our wifi there was down since its dsl and the lines there are down too. So now that I'm home again I tethered to cell wifi to respond to you.

Always remember...

YCGIYWG

(You Can't Get... If You Won't Give)
[Nook Color Android Development] topcaser:
DD, dont worry about your answer speed. You have done a lot of work for the comunity anyway. I appreciate your work.

So i have forgot to mention, that i have already tried to dial the IMEI and the window says nothing, i.e. no IMEI. If you need more information to trace down the problem let me know.
[Nook Color Android Development] DizzyDen:
For top and xtreme...

Try turning ADB wireless off and back on on the Nook... had this problem in the past that if it is enabled on reboot... it fails until cycled.

If it still has problem... try finding busybox installer in market and reinstall busybox as indicated in self-quote below... in any event PLEASE let me know so I can fix any issues... I cannot duplicate what you're seeing.
[Nook Color Android Development] ianPhillips1:
I can confirm that the toggling on off works,been having to do that the last few times.

Ian
[Nook Color Android Development] newellj79:
I may have already asked this but, any chance for getting a Linux version of this?
[Nook Color Android Development] DizzyDen:
Don't recall that one being asked.... I'm on vacation from job next week... so I'll see about getting an on-device app and a linux version together for us... still not sure on feasibility of on-device but we'll see.
[Nook Color Android Development] actorman46:
Linux version would be great! Loved your program on windows but just made the switch to Ubuntu.
[Nook Color Android Development] FlanFlinger:
A stand alone version would be great for those of use with obscure Chinese tablets :D
[Nook Color Android Development] topcaser:
Hi Dizzy,

unfortunately still the same with n173. It appears that everything works fine up to the last two steps: pushing framework.jar and reboot. Pulling the file works pretty well.

I took care after nookies reboot that ADBwireless was not active. I dont know what to do with busybox!!??

So just a question: I haven't older versions of IMEI generator on my computer any more - but it worked pretty well with older versions. Where am i able to download them?
[Nook Color Android Development] DizzyDen:
No problem... just let me know what version you want... I'll take care of you... but... I don't think it will make a difference... it seems like the symlinks for busybox or busybox is not playing nicely... but we can rule it out or help track down whatever change is doing it.

Just let me know what version you want and I'll upload it or send it to you.
[Nook Color Android Development] topcaser:
Let's try 1.5 first. Can you send it via PM? Thanks for your help Dizzy
[Nook Color Android Development] DizzyDen:
IMEI Generator 1.7 uploaded

Current version: !IMEIme 1.7

New features:

Reorganized again... the first question is now to update Dev's ROM since I believe it is the most common use... i.e. update ROM then flash to device.

Various little clean up of code and messages.

BUG FIX

After a couple of reports of In-Place having issues (wording by my error checking) I have rearranged the methods used of renaming original framework.jar and pushing updated framework.jar. Certain setups would cause the generator to fail to mount /system/ properly for read/write access.

Bug reporting thread for !IMEIme

I am still working on getting Linux and on-device versions.
[Nook Color Android Development] DizzyDen:
!IMEIme 1.8 uploaded

Current version: !IMEIme 1.8

Bug reporting thread for !IMEIme

New features:

Ability to set LCD_Density in !IMEIme.ini. This will result in editing of whatever method the ROM is using to set LCD density.

The program no longer places new device specific information at the top if you include Device_Manufacturer, it now searches and replaces the variable instead.

If you have IP setting in !IMEIme.ini and that IP address works correctly, you will no longer get the pop up for entering IP address... it now only pops up if there is no IP address or the IP address entered does not correctly respond to ADB commands.

If the IMEI on device or the generated IMEI matches the IMEI in IMEI.fix you will not be prompted to replace the IMEI.fix file.

Various little clean up of code and messages.

NEW ini setting

LCD_Density = setting this value will result in build.prop being edited to replace current setting. The program checks for all known options for this setting (i.e. ro.sf.lcd_density, qemu.sf.lcd_density, ro.sf.lcd_density.xdpi / ydpi) and modifies the setting.

BUG FIX

After a couple of reports of In-Place having issues (wording by my error checking) I have rearranged the methods used of renaming original framework.jar and pushing updated framework.jar. Certain setups would cause the generator to fail to mount /system/ properly for read/write access. Thank you topcaser for pointing this out.

Bug reporting thread for !IMEIme
[Nook Color Android Development] skwalas:
I will have to try this out. But... I have not felt that I'm missing anything by not having an imei number. what apps still require it these days?
[Nook Color Android Development] DizzyDen:
XDA-Free app for one... I honestly don't know what else any more... but then again... I have an IMEI ;)
[Nook Color Android Development] newellj79:
I concur, Linux or on-device would be great. I to have primarily made the switch to Ubuntu. I can't remember the last time I booted to windows. I really need to though so I can run your program on the latest nightly. Not haveing the xda app sucks!
[Nook Color Android Development] topcaser:
Hi Dizzy,

my Nookie stucks in a kind of recovery menu. See here:

http://xdaforums.com/showpost.php?p=17225290&postcount=1331

I played a couple of days with version 1.6 which failed to push framework.jar to my device. I stopped investigating in IMEIgenerator and wanted to restart Nookie today (a couple of days later with build.props = 160).

Can this stuck in menu be a following error of IMEIgenerator? What can i do next to debug the problem? Thanks for your help.
[Nook Color Android Development] DizzyDen:
Are you trying build.prop edit in rooted stock? I have had problems getting stock to boot with anything other than stock setting... Give me a while and I'll be home. Nothing in the generator should cause the problem... if it has error it won't push anything.

Always remember...

YCGIYWG

(You Can't Get... If You Won't Give)
[Nook Color Android Development] topcaser:
Thanks Dizzy for the quick reply. I thought already, that IMEI is not the problem. Nevertheless, i would appreciate your help: My NOOKIE WONT BOOT ANYMORE. Crying.

No - iam on nightly 175. Just flashed 177 to see, if the problem still persists. n177 dont changes anything...
[Nook Color Android Development] DizzyDen:
Left you PM with phone number... in the meantime... take the card out and boot stock... then power down and put card back in...

Then try "n" as soon as you see cyanogen screen and try selecting eMMC and normal boot.... again power down if it boots... Then try "n" and select SD and normal... it may be something not clearing the BCB
[Nook Color Android Development] topcaser:
Dizzy,

you are my man. My Nookie boots again. Thank you so much. But some strange things happened. Lets discuss this:

1. I started NC without SD card. But the stock did not finished the boot - it hangs anywhere at the splash screen. The only thing i could do was to power off again.

2. I started NC with SD card again and jumped in the recovery. I selected to boot from sd card but the screen went just black. Nothing happened - i powered off again

3. I started NC with SD card again but did not jump in the recovery - did just a normal boot and this worked - but i dont know why and i dont know why boot in stock does not work any more.

Any ideas??
[Nook Color Android Development] DizzyDen:
Ok... what is on eMMC? rooted stock or stock and which version?

The recovery mode black screen I run across when I use an earlier version of SASD that was updated to 1.3... if that's the case... it is trying to install... but no screen presents itself... I can give you a zip file with the 1.3 uRecRam and uRecImg files renamed to uAltRam and uAltImg that you can use in Alternate boot mode and see the penguin and any information.

I'd do a backup... fix stock first (not sure how many SD's you have around)

Restore stock... sideload 1.3 update... get it all working on stock with no SD.

Then:

Create a clean SASD 1.3 uSD card... install CM7 (IMEI'd and any build.prop edits you want of course ;)) and restore apps from backup.

If you have any questions or want any help... you have my number.
[Nook Color Android Development] topcaser:
stock - not rooted. Dont know the version because one of the first things i did was installing cm.

Iam using version 1.3 - nevertheless, the behaviour was as you described: no screen present (still with backlight, but no screen), but nothing happened

Lets see, if this is necessary: i tried to boot again (normal boot in cm) and it worked again. Thats the good news. The bad news: Stock still dont boots - normally i can live with that because i dont use stock anyway. But i dont know if this has some side effects.

Stock hangs at the "n" screen which tells me: "Contains Reader Mobile technology by Adobe Systems Inc."

So what is your recommendation? You mentioned: "sideload 1.3 update". How do i do this?

Give you a call is not a good idea, since: i live in germany (completely different timezone - normally we have to talk around 4pm (german time) i assume) and moreover my english is very bad. But thanks for your offer.
[Nook Color Android Development] DizzyDen:
Sorry... didn't realize you were in Germany... The sideload 1.3 update would be for stock... it hanging on stock boot shouldn't cause any issues if you never use it anyway. So I wouldn't worry about that.

If the SD is booting... I'd just use it... if you have any problems we will get them sorted out.
[Nook Color Android Development] topcaser:
Thanks again for your help.

I just read this instruction to get my NC updated to 1.3: http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/

The instruction says that i have to connect NC to my PC and NC is recognized automatically. Nevertheless, my NC dont boots properly anyway (into stock) and therefore NC is not propably not recognized. Am i right?
[Nook Color Android Development] DizzyDen:
Yeah... to get 1.3 on it we'd have to do 8 failed boots to get B&N recovery to work and let it install the factory file... then you'd have to go through the registeration process on the device... then attach to computer to copy the 1.3 file to the NookColor partition for it to update.
[Nook Color Android Development] paleh0rse:
I believe the IMEI.fix is intentionally left behind so that it can be used to modify all future builds without having to gen a new number... correct?
[Nook Color Android Development] mr_fosi:
Prolly correct, but I don't want to make too many ass-you-me-uptions when reporting results. :D
[Nook Color Android Development] DizzyDen:
I will have to track this down... maybe add a couple of error handling routines to display exactly where the issue is. Any information as to exactly which modifying is causing it would help track it down in the meantime.

1) is by intent... that is how the program knows if you have generated it previously. That is the one file I don't have the program clean up behind itself.

2) will be fixed in the next beta. I haven't seen that and wonder if it is related to above error.... in any event I will include routine to kill adb server.

Again.. wonder if due to above error. Was the one line that was there "getDeviceID()" or "getDeviceID2()"?

The routine for creating the IMEI.fix also includes the code to append the same lines to ".\out\android\telephony\TelephonyManager.smali"

Thank you for your testing and input and information... It is posts like your's that will get the program where it should be.

NOTE: the space in TelephonyManager.smali above is not a typo... it is added by the forum software for some reason. I could code tag it, but didn't see the need.
[Nook Color Android Development] mr_fosi:
Not sure which one it is, since there are no apparent identifying marks. Seems to be the very first "Modifying" window, but I might have missed one if it open/closed very fast.

Could be, but not sure why it would be.

It was "getDeviceId()" and contained the same code as an unmodded smali.

I figured as much, which is why I think it is the modification of the .smali that isn't going through at the very beginning. That would explain why I still get a nice, packed .zip at the end whose contents haven't been changed.

No probs. I can't do the coding but I can do some of the bug reporting.
[Nook Color Android Development] DizzyDen:
I'm pm'ing you a b6-test.... I've added a couple of error check dialogs to help determine where it is failing. I really want to get this isolated and fixed before posting b6

That means it never modified the file at all... the error above is most likely that it didn't find .\out\android\telephony\TelephonyManager.smali... we may have some work ahead of us to determine if the baksmali output folder is different if running from java folder.

And that is GREATLY appreciated.
[Nook Color Android Development] DizzyDen:
Beta 6... OP updated.

Thank you mr_fosi for testing various interbeta tests for me.
[Nook Color Android Development] DizzyDen:
Beta 7 including ADB(WiFi) for wireless adb to obtain serial number.

OP updated.
[Nook Color Android Development] mellopete:
It is b3 that I was using. There is no .zip.tmp. No errors. The TelephonyManager.smali is the same. I used Notepad++ compare, and the hash values match. I will try the latest and let you know.
[Nook Color Android Development] DizzyDen:
Try beta 7... there's been quite a bit of progress and improvements through the day.
[Nook Color Android Development] nolook:
so is Irvin to just flash this inside generated n87 over the original and keep all settings?,
[Nook Color Android Development] DizzyDen:
Yes. It is to generate a correctly formed IMEI based on your nook's serial number and used to update the ROM's zip file... Pay attention to the notes regarding duplicate files in recent updates... you may have to manually add the framework.jar to the zip file with winrar. It would go into system/framework folder in the zip.
[Nook Color Android Development] paleh0rse:
What's the duplicate files issue all about?

I'm seeing it with b7. Of course I'm able to manually patch, or just transfer the new framework via adb to my existing n87 install, but I'm still not clear on what's causing this duplicate file thing... any idea?
[Nook Color Android Development] DizzyDen:
The latest nightlies of cm7 have duplicate files... try updating the framework.jar... or even extracting n86, n87 that I know of with 7zip... it will report and show the duplicate files.

I have posted asking about the files twice in CM7 dev thread... still have no reply.

Those files are why we've been seeing the issue of the ROM zip not being updated. And why I had to resort to current method of saving the framework and manually updating the zip.

I forgot about renaming the files in the zip and removing the dup in my n87... so I wasn't seeing the issue in my testing of my program.

You can see that it is CM7 thing by opening the zip in winrar and going to system/lib... you'll see two files as I listed in the thread there.

http://xdaforums.com/showpost.php?p=14126927&postcount=2562

and

http://xdaforums.com/showpost.php?p=14312624&postcount=2755
[Nook Color Android Development] paleh0rse:
Ahh, ok, I'm tracking... saw you post about it both times, but nobody is responding. Have you asked about them over in the CM forums as well?
[Nook Color Android Development] DizzyDen:
No, I haven't been over there as of yet. I think as another workaround I will enable the IMEI generator to adb push framework.jar to /system/framework if the user wants.

That won't help the updating install ROM zip's until the dup issue is fixed... but then people could install the update... then run the IMEI generator and place patched rom on their nook.
[Nook Color Android Development] paleh0rse:
Personally, I would prefer that method. If you pull the in-place framework, mod it, then push it back, that would be perfect! If you do, then please also copy the old version to framework.jar.bak :)
[Nook Color Android Development] DizzyDen:
Thank you all for the input... I am thinking also about the manual input... but am afraid that may cause us issues with ppl like Swype developers... as I see potential for missuse... but will probably add it anyway ;)

I almost would prefer a random generation of IMEI if adb fails... but will include manual input for now at least.

The method of random I was talking about is simply have the software generate a random 15 digit number and generate an IMEI based off of it. But I like your idea of entering a passphrase and generate a hash... even if simply converting it to ascii hex.... hmmmmmm
[Nook Color Android Development] BitingChaos:
So, um... What can this break (or what trouble could it cause down the road)?

I understand that (dumb) programs that assume IMEI are still assuming a factory-assigned number.

What if a Nook Color's serial # just happens to be a real IMEI number already assigned by another factory for a phone?

Is there a chance there still could be a duplicate with someone else?

I believe Cyanogen said they would never put any kind of IMEI spoofing into the default build of the software. What reasoning did he have?

http://twitter.com/#!/cyanogen/status/73496701691895808

Also, in another forum someone said "It is a criminal offence in the UK to tamper with IMEI numbers."

Does using the Nook Color's serial number simply get around all these issues?
[Nook Color Android Development] DizzyDen:
I personally do NOT see any potential "down the road issues" but am certainly welcome to anyone sharing concerns.

In fact, I started this project to try to AVOID "down the road issues" since so many who needed IMEI for software validation were using the same generic IMEI provided in patches instead of creating their own... So I decided to make an easy method for everyone to create their own.

As I see it.... the possibility is SO REMOTE I would say NO... that is why I chose to utilize "TEST" formed IMEI. I don't think we'll ever have to worry about any hardware manufacturer using a test IMEI that specifically matches one generated from our NookColor Serial Numbers.

The odds are theoretically 1 in 999,999,999,999,999 That's 999 TRILLION with a T or I suppose 1 ZILLION with a Z.

I cannot speak for anyone other than myself... Possibly because no one thought of a way to impliment it to utilize individual IMEI in the packaged framework.jar

I am not an attorney, so I only speak from common sense...

Technically speaking, since the NookColor does NOT have an IMEI number, we are not tampering with it. We are providing a unique solution to a problem that exists.

I hope I have addressed all of your concerns adequately... if not, feel free to ask for more specifics.

BTW... beta 8 up soon... manual inputting a seed or serial number for IMEI generation provided... keep eyes out.
[Nook Color Android Development] topcaser:
"Yeah... to get 1.3 on it we'd have to do 8 failed boots to get B&N recovery to work and let it install the factory file..."

You are joking with me, isn't it? You mean, after 8 failed boots NC recovers itself by entering a certain menu where i can reset the device. Is this cool!?
[Nook Color Android Development] fatalfuryy:
DizzyDen. Thank you for your hard work. App worked perfect for n176.

All i had to do was download the adbwireless app. Provide the ip address when prompted and it created the new zip file. moved all my downloaded apks to my emmc root just to make sure i didnt lose anything and reimaged my SD card.

Was able to load Dungeon Hunter without any issues

Thanks