yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] DizzyDen:
Yes... but we'd wind up with the same debate that has caused me to discontinue my releasing projects... I digress until the one with credentials can provide a solution....

BTW... that's what my intent was... long term... too bad the project manager got tired of defending the project.... Anyway... this will be my last post or edit in this thread... because any more will include more quotes an dizassemblies of the bull**** that caused discontinuation.

I do anxiously await a fix from one who feels their credentials are more significant that others.
[Nook Color Android Development] actorman46:
Dizzy, thanks for all your work. I had been following this thred, and I think it's wonderful what you were trying to do. It was sad he had to do what he did, and I don't blame you for backing out. These threds shouldn't be a place to argue.

A question for anyone else still poping their head in,

I was out of town and didn't get a chance to try this out, could someone post a link? Thanks in advance.

ANd thanks to Dizzy and everyone who put time into this project.
[Nook Color Android Development] BitingChaos:
Obviously, this wasn't true.

We're not all developers or Android hackers. You made something interesting and a lot of people were then looking up to you - in a very short time.

This thread got over 4,051 views in just 5 days. You're letting a lot of people down by taking everything back, giving up, and then telling *us* to do it ourselves. To start it all from scratch. To re-learn and re-do everything you just did.

And why, because one person angered you?

What about all the people that really appreciated what you had done? All the people that checked this thread several times a day, just to see what amazing improvements you had made? What about them?
[Nook Color Android Development] DizzyDen:
I swore to myself I would only check the thread and never reply to it again... but this post along with PM's I have gotten has caused me to reverse myself.

I do want to thank everyone supporting my efforts to provide a solution to a problem we Nook hackers face.... it means so much more than you can ever imagine.

I honestly have never kept up with views, replies, downloads, etc... I wound up focusing on replies... and that is where I got to the point I felt it wasn't worth it.

I truly appreciate those that have stood up and supported my efforts publicly, as well as those that supported it silently.

The quote you so elequently used was extremely sincere... it was when I was beating a dead horse that it became tiresome.... I did welcome, discuss, evaluate and explain my decissions. It just seemed the thread took a very negative turn for something intended to be so positive for the community.

I was in NO WAY telling the USERS to do it themselves, I was telling the neighsayers to provide a better fix for us.

I can honstly say... I have had tears in my eyes responding to some pm's regarding my decission to discontinue. I feel my decission may have been more haste than heartfelt... but I am just plain wore out discussing why one method to generate something we don't have is better than another... especially when I have to truncate somewhere....

The funny thing is... if I had left the METHOD I used out of the OP initially, there would have been no bull****... but, being the up front kind of guy I am, I felt obligted to let users know the last digit was not being used... I just got extremely tired of defending my reasoning and having to explain why another method is no better.

Let me get some sleep and I will reconsider whether to continue developing releases worhty of the community.
[Nook Color Android Development] liqn7:
Please dizzy continue your fantastic work and ignore the naysayers. If they don't like your work, or don't appreciate all the effort you've put in to solve a problem which has been ignored by other developers, then I say screw them. They don't have to use it or even read this thread for that matter.

For every ignorant and negative comment, there must be hundreds of other delighted, silent but appreciative members who love what your doing. :) (myself included)

You have gotten the furtherest in addressing the imei problem, and I implore you to continue.

Either way, thanks a million for all your efforts thus far. Hope it can continue :)

Cheers
[Nook Color Android Development] mr_fosi:
Well, it's yer project ol hoss so you say when it's done.

I hope you decide to leave a release up though.

I didn't get a chance to grab b9 but I do have b8 and am willing to post it.
[Nook Color Android Development] paleh0rse:
This. Some of us supported you from the start and stayed out of the argument. Please just ignore the one guy and continue to work with the rest of us who enjoy testing your software.

I, for one, was really looking forward to the version that might work with an already-installed build, and I truly do appreciate everything you are doing....
[Nook Color Android Development] rhester72:
DD, as I stated in my PM, as long as you're willing to help people fix their devices when their IMEI changes without warning in the future and all their software breaks, and you're willing to take responsibility for having Nooks blacklisted with software retailers on the Market because you couldn't wait to be a hero and listen to dalingrin nicely tell you to back off, it's all good. I'm well and truly done with this...I should have expected a gangbang of fervent users attacking me as a 'bad guy' because they are willfully ignorant of the risks they are taking (and that you conveniently forgot to tell them about).

I *WILL NOT* reply to this thread again. Quit, continue, do whatever you like...but you'd damned well better take responsibility for the outcome in the future.

Rodney
[Nook Color Android Development] DizzyDen:
I have seen NOTHING from Dal in this thread at all... I do recall seeing a dev highly recomment people not use the patches that used the "generic" IMEI...

Again... I will state.... this is NOT geared at ANY AOS specifically... get over yourself.

Why does this project require me to assume any resonsibility for an outcome than any other... who tend to specifically state that the author is not liable for any bad that can come... and this damned sure won't brick anything.
[Nook Color Android Development] paleh0rse:
Many if us know the "risks" just as well, or even better, than you... and many of us also believe that this solution mitigates those as well as any other could. AFAIK, the cm team will NEVER allow another IMEI commit for the simple fact that they plan to avoid any/all contraversy dealing with IMEI. For that reason, any possible fix must come from a third party -- like this one.

I feel that Dizzy's method of IMEI generation provides a test number that is unique enough to avoid the wrath of any vendor. And, even if any dev still decides to take action against our set of numbers, I also feel confident that we can then find a new way around said action if/when that happens.

You've said your piece, as you're entitled to do... but, I ask that you now let the rest of us decide whether or not the "risk" is worth it.

Dizzy -- please know that you have no such "responsibility" in the future. As testers and fellow hackers, we know wtf we're messing with. Please continue on and ignore those who might criticise while offering no alternative solution of their own. Rodney might think he "knows better" than the rest of us, but he doesn't.

PS: nobody from teamdouche, including Dal, has ever stated the serial number solution is a bad one. They certainly didn't recommend the original method of everyone sharing one IMEI, but they've not said word one about this one. Besides, this project has nothing to do with CM specifically... please keep it going! :)
[Nook Color Android Development] 12paq:
Java path is correct, but thanks. Let me fiddle with it more and study the op better. Like I said, its more likely something on my end.

..and thank your for time and efforts with this project, its greatly appreciated.
[Nook Color Android Development] DizzyDen:
You may need to insatll 32 bit java and run from there... I know some other software require it... and since this is written to be functional on 32 bit systems... it may be a requirement... it is the use of baksmali and smali within the java console that would require this... MS's IE being one of them.

I know on Sun's java downloads, it detects your browser and recommends downloading both if you are using 32 bit and 64 software.

IF this turns out to be the case... please respond so everyone using 64 bit windows will know... I suppose I can place it in my 64 bit and test... but have to modify my path to eliminate java from being on it....
[Nook Color Android Development] TheMainCat:
Read that part. Message is from the java/bin folder when I ran the exe
[Nook Color Android Development] DizzyDen:
OP updated, b9 uploaded....

I apologize to the community for my short sighted reactions to attacks at my methods, work and efforts. I assure you that will not happen again. I have come to realize the support and appreciation is far greater than I imagined. THANK YOU!!!

Now.... back to testing ;)

PLEASE feel free to provide any feedback and/or bug reports... just don't continue to push your ideals once it has been discussed... beating dead horses gets tiresome and just wastes precious time.
[Nook Color Android Development] jjvcuyler:
See, I'm the exact opposite. I don't care if anyone knows my MAC, but I'd rather not publish my serial number.

There is absolutely no reason to protect one's MAC. It's meant to be and is public information. When one attaches a device to a network, every other device on that network has access to its MAC. It's broadcast for all to see.

On the other hand, the serial number of a device would certainly be handy to have during some sort of social engineering...
[Nook Color Android Development] DizzyDen:
Removed due to inaccurate assumptions... apologies made later in thread.
[Nook Color Android Development] frankusb:
Just tried b9, on XP 32 bit, I get !IMEIme.exe is not a valid Win32 application. Java is in my path. I tried as admin and user, same message.

Frank
[Nook Color Android Development] DizzyDen:
Thank you for the bug report... have you used any prior betas of the program?

I ask because it may be due to new message box icons I added.
[Nook Color Android Development] jjvcuyler:
Chill man. I'm not one off the assholes who have been jumping all over you. I have no agenda. I think you're doing great work, and I'm certainly glad you're back. So get over yourself.

I made a humble suggestion, during a time when you and others were discussing how to get the generated IMEI unique. From your reply a few posts later, you were at least intrigued. The next time I posted was in reply to someone else, someone who claimed using the MAC would be "hard". I simply explained how it would be pretty simple. You replied at about the same time with basically the same information. Whether or not you agree with the solution, we agree it would be easy to implement.

However, when you're posting incorrect information, in this case that someone discovering your MAC is "bad", I'm going to correct you. Because that is blatantly wrong. Not to worry, though. There's no shame in being wrong.

You want to protect your MAC... now that's really a laugh... I guess it's possible, if you never ever connect to a public wifi. I can go into a Barnes and Noble, join their wifi network, type, "arp," and get the MAC addresses of every device connected. The Nooks will be the ones that start with, "58:67:1a". They all do.

Finally, discussions on generation are dead until an argument is presented that can persuade you... How will anyone know which argument will persuade you until it is presented to you and is accepted or rejected?

Once again, I'm really happy you're back to working on this. Good luck.
[Nook Color Android Development] DizzyDen:
I will apologize to you publicly... Perhaps it was the timing of the posts that lead me to believe you were just another attacker... I am sorry for that assumption.

I can honestly still see merrits for using MAC address, the same as I see merrits for using the serial number... the truth is... either is sufficient to provide the programs intent... and neither being exposed warrants concern.

Hell in b10 I may just opt to give the user the option to use serial number or MAC... should keep everyone happy :)
[Nook Color Android Development] frankusb:
This is my first try. I have not run any prior betas but would be glad to try if offered.

Frank
[Nook Color Android Development] DizzyDen:
I will upload all past beta's I still have to my RS fileshare... I would suggest starting with b7 and back... you should be able to cancel at any "open zip" dialog and it exit the program... Just trying to figure out at what point I broke 32 bit support.

More to come as soon as they are uploaded.
[Nook Color Android Development] clamder:
I'd like to add a +1 to this. Thanks for your continued work on this! I would definitely use this if there was a mac add option. I don't know how many octets you'd have to chop, but I would chop the 1st octet as the 2nd and 3rd should sufficiently provide the vendor in our case. Just a thought.
[Nook Color Android Development] DizzyDen:
Everything from b2 up is here. You may have to browse to the IMEI generator folder there... seems RS keeps changing the way they link to the linklists.

Actually, if I recall correctly from my research... I believe it would only be the first octec.... however, truncating the first two out would allow a more reasonable "real" feel of the 17 digit IMEI... as the last 3 digits are designed to be SW version.

I have always kicked that idea around since it was first mentioned... it was only one person's attitude that had caused stubborness... I apologize to the whole community for letting that effect a solution. I will try my best to not let personal feelings impact development in the future, and I have no intentions to abandon this until a real solution is provided.
[Nook Color Android Development] jjvcuyler:
No worries at all. I'm just trying to be helpful in this thread, and I don't want to be perceived as a troublemaker/troll by the guy doing all the work, because then if I ever get an idea you might like, it'll be ignored. ;-)
[Nook Color Android Development] DizzyDen:
No worries...its all good.

I am sorry if I have come across as close minded... I have been weighing merrits of any method I can come up with... and I do sincerely appreciate feedback and discussion that ensue.

The rest has already been expressed a couple of posts up by me. (the one regarding my stubborness ;))
[Nook Color Android Development] frankusb:
Beta 9,8 and 7 all do not run for me on XP 32 bit. Beta 6 does run for me, now to see if I can have it patch the latest nightly.

Thanks for posting the builds.

Frank
[Nook Color Android Development] DizzyDen:
Beta 6 SHOULD work.. .I will look into the changes between 6 and 7... that may be version where I added new icons to message boxes.

Wow!!!! the thing about this issue is that 7 is where I included manual input, and I don't see anything in that code that would be windows version specific... Going to try one thing... I will upload an alternate beta 8... will call it beta 8.1 for you to try... IF it runs please let me know... then I will know what is causing the x86 issue you are seeing.

OP updated with newer beta fixing the issue.. and working around another for now.
[Nook Color Android Development] cmstlist:
Same on Win7 32-bit with version 9:

Downloading b6 now...

b6 runs but it told me ADB isn't working (although it is) and thus used the generic IMEI. Damn. And it didn't provide the the option to enter the ID myself - I guess this feature was added in the newer-but-broken versions?

Wait, even stranger, it *does* read my serial number properly, but then still says "Failed to read DeviceID".

Okay, tried the "8.1 beta" and it does work, reads everything. Going to try it out now...
[Nook Color Android Development] DizzyDen:
It was added in beta 7... try the beta 8.1 that I added in my edit to post right before your's.... I was adding when you were posting....

Thank you... looking forward to your further comments regarding beta 8.1.... It seems it was compiler options that was used.... honestly... it still makes NO SENSE to me... I have no version specific directives included.
[Nook Color Android Development] cmstlist:
I manually replaced the framework.jar by ADB. First reboot after took maybe 5-10 minutes. Then I installed proper Swype Beta, and it works great! It's so wonderful to be using a version that has had the most recent bug fixes rather than an old hacked one.

Rebooting one more time to make sure the Swype license still survives... YES! Thank you again.
[Nook Color Android Development] DizzyDen:
Now that we have the windows version issue resolved... I will get back to work on beta 9.... As soon as I figure out what I broke in it, we'll have adb pull, adb push included again for in place updating.... I had it working... then was tweaking some code and borked it up... I'll get it fixed up soon though.
[Nook Color Android Development] cmstlist:
I wonder if it might even be feasible to develop an on-device version? Obviously you can't replace framework.jar while booted into the OS. But perhaps an apk could be created that produces the modified framework.jar, packages just the one file into update.zip format, and then reboots into custom recovery to apply it. :)

But alas I'm not a programmer, just a very hacky user.
[Nook Color Android Development] TheMainCat:
B8.1 runs but I get a AutoIt error message box: Line 1916 (error in expression). I get this error after clicking "yes" when planning to update a dev's zip ROM (first yes/no box)
[Nook Color Android Development] DizzyDen:
I will see if I can determine the issue. Does it provide you with a filename asking if it is the right one? Does it pop up a window that says searching for ROM or anything else prior to the error?
[Nook Color Android Development] paleh0rse:
You can alter, delete, and/or backup the framework.jar while you're booted into the OS. In fact, I use root explorer to do exactly that every time I drop in a freshly modded framework file. :)

It simply requires a reboot before the changes actually take effect.
[Nook Color Android Development] TheMainCat:
Nope. Nada. As soon as the "Yes" button is clicked, it all over Johnny. No other description is provided, just line 1916 which is probably the start of a function call :D
[Nook Color Android Development] DizzyDen:
That error is due to there being NO .zip file in the folder at all... I will fix that issue... in the meantime a work around is to copy the update zip to the folder the program is being ran from... or create a BS zip file there and select no when it asks if it is the right file.

I just copied my program to a blank folder... got the same message... created an empty text file (only because it was easiest for my test)... renamed it to !blank.zip and the program ran fine.

Actually... further testing revealled NOT fine.... OP updated with beta 8.3 that at least provides an ugly work around for now... even if there is no zip file in the current folder... it will pop up a window saying ROM file found.. it just won't have a name and you will have to click no.
[Nook Color Android Development] DizzyDen:
The long (enough) waited for beta 9a is posted. OP updated.

We now have a means of in place updating framework.jar.

Please realize, as I add more features, it becomes more difficult to solely test all possible combinations of what a user may experience... i.e. I have to verify against several different combinations of configurations and button clicking... I try very hard to release bug free... but I will certainly squash bugs as quickly as I can.
[Nook Color Android Development] Ang3lmack:
So how would this work if I'm using dual roms? Like the phiremod and honeycomb combination
[Nook Color Android Development] DizzyDen:
The in place update would probably not work. However the rom zip updating would still work perfectly well.... you'd just have to do it to both ROM's zip files.

However... you could try this....

Boot into one system... use the adb pull function on that... move the file to a temp directory...

Boot into the other system... use the adb pull function on that one...

compare framework.jar's to see if it does in fact pull from different ROM's... IF it pulled the framework.jar from both systems, it will work perfectly fine.

Thinking on this... it SHOULD work just fine... it would pull the framework from /system/framework for whichever AOS you are currently booted into... do its thing... copy current framework.jar to framework.jar.bak and push the modified one to /system/framework.

Then you would boot into other AOS and repeat.
[Nook Color Android Development] Ang3lmack:
Sounds simple enough, thanks
[Nook Color Android Development] paleh0rse:
I tried b9a, and everything appeared to work initially when modifying an in-place framework -- in this case, I'm on a virgin n93 install. However, the last dialog that popped up from your app was "Do you wish to push the modified framework.jar to the device?" After that, I'm not sure if it actually did so since nothing else ever popped up...?

If successful, does it place a .bak version (backup) of the original framework file somewhere? Is there supposed to be a "framework successfully patched and pushed" message of some sort?

I'm going to reboot to see if it worked... I'll report back.

Update: it didn't take. there's a new framework.jar in the b9a app directory, but it never pushed it back to the nook. I'll try a few more times and report back.

Update2: tried several times. it's simply not pushing the newly modified framework back to the nook after I tell it to.

Update3: I manually pushed the new framework.jar that showed up in the b9a directory, but it doesn't appear to be modified -- after a reboot, HBO GO force closes on "sign-in" just as it does with virgin frameworks. :( I'll try to mod the zip instead...
[Nook Color Android Development] DizzyDen:
First... let me apologize for taking so long to respond to this... I was at work when the post came in... just now walked in the door....

I was intending to get checks and reports regarding success or failure of the adb push and just didn't have time... I wanted to get what I thought was working available, then add the screens.. just not enough time to incorporate the popups into it before I had to get some sleep for work.

I will look into this... Is there a framework.jar.bak in /system/framework ?

I'm betting not... I know what I did... forgot to remount /system as r/w.... silly mistake. Beta 9b will be up in just a little while.

In the meantime, manually updating framework would impliment the new IMEI...

As fare as HBO Go FC's... I don't know if it is due to your IMEI changing from what you registered or what... this would do nothing to facilitate anything within any app other than report your IMEI.
[Nook Color Android Development] martian21:
I'm almost certain this is the case. I'm not an HBO Go subscriber but I do know that Swype promptly stopped working when I changed my IMEI so I'm not surprised that other apps are doing the same. Swype allows you to changes devices (ie. change IMEI numbers) once, after that you need to create a new account.

Perhaps there is something similar you can do in your HBO GO account?
[Nook Color Android Development] paleh0rse:
Actually, the framework.jar created by version 9a was somehow defective, or not properly modded. I reverted to version b7 and created a new nightly-93 framework without any issues, and HBO GO worked again.... So, while I know b9a didn't push the new framework, I'm not sure it ever modded it either.

This wasn't a case of changing/registering new IMEI's with HBO...