Hey everyone,
I rooted my NST Glow for the first time about a month ago and I was an idiot and didn't take a back up first. In the process I managed to totally mess it up. It got so bad that it was bricked and wouldn't boot no matter what I tried. Eventually I decided to try taking a backup of my wife's NST with glow and restored that to my Nook. That worked and allowed me to do a wipe, then root it properly etc. So everything was working and seemed good to go.
Today I was rooting my wife's nook and in the process put it online. At some point it said that there was an authentication error and it rebooted the nook and wiped it to factory.
I restored her nook from the fresh backup I took and it is back up and running, however it is unrooted and offline. My guess is that I cloned her nook's ID to mine when I restored from her backup and now B&N thinks that our nooks are the same device and registered to two different accounts. Thus anytime hers gets online it will get wiped.
Is there any way to reset my Nook's device ID or w/e so that it is unique again? How do I fix this problem?
And yes I learned my lesson and take backups regularly now.
unfortunately mate , we dont have any method to recover thr Rom partition that have ur unique files like nooks ID and MAc address and serial and etc , so i think if u dont have any chance to find an backup for ur device , then noway mate
but , u can use one device for online purpose and other offline always and for ever until u got recover ur original Rom partition
sry for ur loss mate , but try to remember that u take backup or anything or ur nook just will be used offline only
good luck
speedman2202 said:
unfortunately mate , we dont have any method to recover thr Rom partition that have ur unique files like nooks ID and MAc address and serial and etc , so i think if u dont have any chance to find an backup for ur device , then noway mate
but , u can use one device for online purpose and other offline always and for ever until u got recover ur original Rom partition
sry for ur loss mate , but try to remember that u take backup or anything or ur nook just will be used offline only
good luck
Click to expand...
Click to collapse
You could always try using Noogie to get at the rom partition - the S/N and MAC address are just text files
down in the devconf subdirectory on the rom partition. Nothing special, except no line termination.
If I were doing this from linux/Ubunto, I would try something like this after booting Noogie and attaching the
nook to my laptop, and assuming that Ubuntu mounted the Noogie-presented rom partition as /media/ROM:
echo -n "XXXXXXXXX" > /media/ROM/devconf/SerialNumber
echo -n "XXXXXXXXX" > /media/ROM/devconf/DeviceID
echo -n "58611Axxxxxx" > /media/ROM/devconf/MACAddress
If you log into your account on www.bn.com, go to manage your Nook, and put the pointer over the nook in
question, it will show you the S/N registered to that particular device associated with your account.
Of course, you say that you re-registered the nook, but if you're lucky, it will show up as a different device
under the management window(since it probably presented a different S/N from the original). Just ignore
the device with the S/N that matches what's in your cloned ROM(that S/N belongs to your wife). Hopefully
the original is still showing up as another Nook, which will have your original S/N. Put that into the
SerialNumber and DeviceID files.
As far as the MAC address, other than the 58611A prefix, which you need to leave the same(it's the manufacturer
code), pick a different series of six hexadecimal digits that are different from what you already have.
The MAC address only needs to be different from any other device attached to the same WiFi router.
If you pick something at random, you know it'll be different from your wifes Nook, and you've got a good
chance that you won't match anybody else that you're sharing a Wifi router with(at home, or the BN store, etc).
They must be 6 hexadecimal digits, and I would keep any alpha characters uppercase. Or you could just
pick 010101
What do you have to lose? I'm just guessing that this will work, but at this point what other options do you
have?
PS: If you do try this, please keep us updated.
Sure you can fix the serial number and mac address but you can't recover the public key and private key hash you need to authenticate with B & N. Fixing the serial number and mac address will keep you from messing up your wife's B&N authentication and allow you both to be on the same WiFi access point at the same time. But its unlikely you'll get B&N Authentication to work with the native NST apps. But you might be able to install the Nook app from the Market and use that to read your B&N books.
straygecko said:
Sure you can fix the serial number and mac address but you can't recover the public key and private key hash you need to authenticate with B & N. Fixing the serial number and mac address will keep you from messing up your wife's B&N authentication and allow you both to be on the same WiFi access point at the same time. But its unlikely you'll get B&N Authentication to work with the native NST apps. But you might be able to install the Nook app from the Market and use that to read your B&N books.
Click to expand...
Click to collapse
So this has already been tried, and it's known that the public/private key is used
to identify the specific Nook(not simply used for comm encryption to the BN server)?
If it were being used to identify the Nook shouldn't there have to be a full private key
half, as opposed to simply the hash? The only full "piece" of a key that I see is
the public half of the key, which you wouldn't normally use to specifically identify a
device.
Even then, even if it's a device identifier rather than a pre-loaded SSL or comm pubkey
for connecting securely to the Nook server(s), do we know that B&N has matched that
key to the device S/N, and keeps that matchup in a DB somewhere?
If not, then it should be possible to create a new key. You may lose the original registration
info, but re-registering should be possible.
Has anybody actually tried this yet?
...
Hmm, I just diff'ed the Pubkey in the rom backups for my NST and NST Glow, and
they're different, which doesn't make sense if it's an SSL/Comm pubkey being
used to connect to the same B&N server(s).
Thanks for the responses guys. It looks like I have made an erroneous assumption. I stumbled across this thread which says that the Nook Color Tools causes the factory reset, and that is exactly what I was doing when her nook reset on me.
I assumed that it was because I put the nook online for the first time since restoring mine with her image and B&N detected that they had the same ID or something.
When I get a chance this week I will check the serials and stuff in the ROM partition on both the nooks and see if they are the same or if mine is still unique from hers. The B&N website is only showing one nook under my account but says it was registered Sept 2, 2012 (long before I rooted it) and it lists a serial number there, so I am hopeful that my nook is still unique, and if not I may play with it and see if I can return it to the original serial. If I lose the ability to sync to B&N that isn't a big deal since I only have one book on my account (I sideload all my books through Calibre).
I'll let y'all know what I find out.
Here's a Nook Tablet users experience with restoring the serial number and mac address. Bottom line is he couldn't authenticate with B&N after restoring the serial and mac. He ended up lucky and got B&N to replace it under warranty.
serial number can found in the NST original Box , or u can found it when u look in memory card slot
for Mac address , i dont know how , but u can use cheat one , for how to edit , add this info to Rom partition , i dont know
good luck
You can follow that: http://forum.xda-developers.com/showthread.php?t=2104145
I faced a same situation and now my nook become normal :victory:
thanmeo78 said:
You can follow that: http://forum.xda-developers.com/showthread.php?t=2104145
I faced a same situation and now my nook become normal :victory:
Click to expand...
Click to collapse
That thread tells you how to save your ROM partition before overwriting it with a backup from a different Nook and then replacing the ROM partition with your backup. Unfortunately, it appears the OP had already restored a backup of another Nook before saving his ROM partition so the procedure on that thread is unlikely to do any good at this point.
Yah, unfortunately I did not back up my own ROM partition before writing a new one. I tried putting in my serial and changing the MAC address, but as in the other thread I could not register with B&N as I'm assuming the private keys don't match my serial (as they came from my wife's nook). So unless someone figures out how to recover or generate a new private/public key pair that will work with B&N's servers, I'm stuck with a cloned nook.
It's ok though because I side load all of my books and don't need to have it online or anything. So, it is working just fine for my purposes at this point.
Related
I need a .img of the original rom, where can i find? Thanks
Aran83 said:
I need a .img of the original rom, where can i find? Thanks
Click to expand...
Click to collapse
You cant, every NST is unique and using an image from another NST will cause trouble for both you and the NST it came from.
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Aran83 said:
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Click to expand...
Click to collapse
There's no img you can install.
You can try booting n2T-Recovery (v0.2) from a SD card and see if that helps. (Do not write that image to your NST!)
If not, send me a PM and I'll try to help you out
Something else you can try:
1) Flash noogie.img to an sd card.
2) Hook up your nook to a pc via usb once it has booted, and you should see all the partitions exported there.
3) In one of those partitions (recovery maybe? I'm struggling to remember), there's a factory.zip, which you can then install using the "Install from zip" feature of clockwork mod.
If you go this route, you'll have to reflash your sd card with clockwork mod after you've extracted the factory.zip using noogie.
Seems like kind of a pain, but I just recovered my device using this.
Remains in the screen ROOTED FOREVER and i can't do anything
I think, for michaelwill's method, you need to have linux running. I suggest you to try ros87's suggestion.
if I use backup from nook of my friend?
Aran83 said:
if I use backup from nook of my friend?
Click to expand...
Click to collapse
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
herofmm said:
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
Click to expand...
Click to collapse
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
This includes:
Serial Number
Main Board Serial
Product ID
Manufacturing date
SHA hash of Private Key
Public Key in modulus form
WiFi Calibration file
Some unique binary file for your eInk screen
MAC Address
Battery Type
Duplicating the serial will make you or your friend unable to register with B&N
Duplicating / Faking the private/public key pair, will most likely make you unable to register with B&N (I'm currently testing this)
Duplicating a WiFi calibration can cause degraded WiFi performance
Duplicating that EPD vcom file (eInk screen).. well who knows
Duplicating the MAC will cause network troubles if used on the same network.
The wrong Battery Type (I've seen three different so far) can cause charging troubles, and will cause incorrect charge indication.
Don't go there!
NookRestore.img
Try writing NookRestore.img to an mSD card. (You can get a copy at my website: NootRoot)
Hard reset
I had issues rooting my NST and got stuck in a boot loop. After digging and digging through forums I finally discovered the secret to a hard reset. The instructions said to hold the power and the two bottom side buttons down together for over 20 seconds. That worked! My NST was back to when I pulled it out of the box. I then proceeded to re rooting. (my mistake was I did not upgrade the OS before rooting). My bad. Hope this helps someone recover from a stuck boot loop.
Good luck.
chucktate said:
My NST was back to when I pulled it out of the box.
Click to expand...
Click to collapse
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
ros87 said:
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
Click to expand...
Click to collapse
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
sokoow said:
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
Click to expand...
Click to collapse
That is correct.
Problem is that most people who end up in a state where Factory Restore doesn't work has usually managed to overwrite their partition tables and part of the /rom partition.
And at this point it is too late to backup rombackup.zip as it's usually fragmented and cannot be recovered by ext2 file recovery tools.
So.. do a full backup before you do anything to your NST
I found if you restore with holding the two lower buttons it will remove all rooted files.
Googie2149 said:
I found if you restore with holding the two lower buttons it will remove all rooted files.
Click to expand...
Click to collapse
Read post 13 by ros87!
ros87 said:
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
Click to expand...
Click to collapse
Go to my website, download nookRestore.img and write it to an mSD card, Erase and De register, Power Off, then insert mSD then power up, then follow on screen instructions!
[OT - Removed]
[OT - Removed]
Torimu.Joji said:
I'll update the website and post links to XDA.
Click to expand...
Click to collapse
Thank you sir!
By posting proper links you help ensure that people get the most recent software and information
Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
dukenookem said:
Guys, I had quite bad experience rooting my glowlight nook with touchnooter . Basically messed smth up so it couldn't start (just kept flashing). didn't save my back up. had to do unrooting with the software 1.1 that I guess was from nook without glowlight. Unrooting went fine, but the glowlight function is not working anymore. does anyone know how to solve this or could give me a link to download the proper software? thanks!
Click to expand...
Click to collapse
you should read the instructions better next time...
but making errors is human and you have a cool nick
I'll hopefully receive my glow in two weeks and I'll upload my backup then
You should make an effort to salvage your personalized data in /rom.
There is all the info in the p2 partition (/rom).
There is also a backup copy in the p3 partition (/factory) as rombackup.zip
You might do this with noogie or CWR and ADB.
Zorkman said:
you should read the instructions better next time...
but making errors is human and you have a cool nick
I'll hopefully receive my glow in two weeks and I'll upload my backup then
Click to expand...
Click to collapse
I could use that backup too, to revive my nook =)
I have an open thread here with all the efforts done so far http://forum.xda-developers.com/showthread.php?t=1805936
Nook Glow Backup Image
I have a backup image of a NSTG that I am uploading right now ... and looks like it just finished. Here it is:
dl[dot]dropbox[dot]com/u/98836278/nook-glow-backup.img
When you have the image downloaded follow these instructions:
blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
As a new user I am not allowed to post outside links.
Downloading, thank you so much!!!
I'll post again with the results...
YES, YES, YES, YES !!!!!!
leadbella thank you a million times!!
I downloaded the image, and wrote it ot my nook.
By the end of the operation, which took some 9 minutes or so, the process ended abruptly:
error 27 writing to disk at sector 3825664
I opted to ignore it and reboot the nook, just to see what happened. The nook booted alright.
I then booted in CWR and replaced /rom with the contents of my own nook /rom which I had salvaged.
I then booted again, and performed all the process flawlessly.
So far I have registered the device again (no error here since /rom contains my sensitive data. Don't know if it would work if the data was from the original image, since MAC address, device SN and some other parameters would not match), loaded a couple of books and started reading again.
Just in time for another one week shift (leaving tomorrow)
Leadbella you saved my..... nook =)
Thank you, I owe you one.
No problem at all. Looks like it worked for srgarfi ... dukenookem please let me know when you have finished downloading the image. I need to use my dropbox for other things at some point, but I can keep it in there until you finish downloading the image. If the image link above no longer works and anyone needs a copy of this image feel free to send me a message and I will try to post it back up.
The image is from a just out of the box NSTG with no information and nothing added to it.
leadbella said:
No problem at all. Looks like it worked for srgarfi ... dukenookem please let me know when you have finished downloading the image. I need to use my dropbox for other things at some point, but I can keep it in there until you finish downloading the image. If the image link above no longer works and anyone needs a copy of this image feel free to send me a message and I will try to post it back up.
The image is from a just out of the box NSTG with no information and nothing added to it.
Click to expand...
Click to collapse
Thanks Leadbella. Downloaded the backup. Tried to follow the instructions, but the size of you file is almost 2 gb, too large for my microSD. Didn't expect the backup file to be that large. gonna go look for a larger sd card.
Renate NST said:
You should make an effort to salvage your personalized data in /rom.
There is all the info in the p2 partition (/rom).
There is also a backup copy in the p3 partition (/factory) as rombackup.zip
You might do this with noogie or CWR and ADB.
Click to expand...
Click to collapse
That totally didn't make any sence to me. Sorry for my ignorance. Are there any instructions to follow? thanks.
Could not register
Hey leadbella, thanks for uploading the backup image. I downloaded and worte it to my nook STG. However, I couldnt get pass the setup process. Everytime I reach the log in menu, it will have the error logging in msg. Do you know what might be wrong?
Zaotr0pe said:
Hey leadbella, thanks for uploading the backup image. I downloaded and worte it to my nook STG. However, I couldnt get pass the setup process. Everytime I reach the log in menu, it will have the error logging in msg. Do you know what might be wrong?
Click to expand...
Click to collapse
You should have saved your /rom files before ovewritting your nook with leadbella's image.
And I'm afraid there not anything you can do to recover your unique /rom files for your nook now.
Oh, I was concerned that Leadbella had posted an unedited backup...
so, what is going on?
first: if a post about partitions isn't comprehensible to you yet -- you probably shouldn't root your device until you do enough reading that you understand it a bit.
Putting leadbella's file onto an SD card probably won't work as a way to restore; when I recover from an image, I use a usb cable and write from my computer to my device.
Leadbella seems to have taken a complete backup image from the device - this will include the important /boot and /system partitions (which is good) but will also include the /rom partition, which unfortunately is unique to every device.
So, if you restore from that image and don't have access to your own /rom partition or recovery image, you're going to wind up attempting to register a second copy of Leadbella's Nook to your account. Fortunately for Leadbella, that won't work.
Now, what can you do to repair and get a corrected nook which can be registered?
I'm going to try an experiment - I'm going to start by backing my device up in its current state.
(I do this by making a Noogie disk
Booting from Noogie
Connecting to my computer
using the command dd if=/dev/sdX of=/dev/currentnookglow.img bs=1M
where X is the number of the device that pops up when I connect my NSTG to the USB port.)
That requires linux; if you don't have linux, you can install VMWare Player (Free) and then install linux in that.)
What I'm going to try doing:
- back my system up
- image with Bella's file
- delete the file /rom/devconf/MACAddress from the imaged device
- reboot the device
- see if I can now see the real, physical MAC address, either on the device (unlikely) or on my router (likelier)
If I can see the MAC address, recreate the file with the correct values for Mac and also create a correct file for serial number /rom/devconf/SerialNumber
Boot, and see if the device is registerable to my account.
BUT: right now, BN has blown out the Nook Touch register/deregister/register process. So I can't do the test until they fix that.
And if it does work, anyone trying it will need
- the noogie disk
- linux
For windows users, maybe, but I have not tried:
- a clockwork boot disk
- functioning ADB able to connect to your clockwork-booted device
(Some clockwork boots support ADB; some do not.)
as roustabout explains, you can write Leadbella's image to your nook (if in windows use win32diskimager or diskimage) and then take a look at the contents of /rom.
The fix the contents of macaddress and serialnumber, but only if you plan to use the nook with B&N services fix the rest of the necessary files.
If you just plan to use your nook as a standalone reader (yes, why not?) once registered you can just ignore the contents of /rom (at least until the next software update).
leadbella said:
I have a backup image of a NSTG that I am uploading right now ... and looks like it just finished. Here it is:
dl[dot]dropbox[dot]com/u/98836278/nook-glow-backup.img
When you have the image downloaded follow these instructions:
blog[dot]the-ebook-reader[dot]com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
As a new user I am not allowed to post outside links.
Click to expand...
Click to collapse
These links are both no longer available. Can someone post them to a mirror?
I'd really appreciate reup as well, since my backup is not working and I need to restore my NSTG.
before restoring from someone else's img, remember to salvage your own /rom partition since these files are unique to each device and you'll need them to register your nook prior to starting reading.
That said I can upload that IMG, but what's the best choice to do so? Any of the many filesharing services? Dropbox ? Google Drive?
require those images
Hi srgarfi, is it possible for you to please upload those images... i need them...
Please reupload the backup. I could really use it too.
the image I used, originally shared by LeadBella (thanks again!) is here:
https://www.dropbox.com/s/xikkjs627s9mw2r/nook-glow-backup.img
Remember to save your /rom files before applying the backup or you won't be able to register your nook on B&N to start reading.
Hi,
First off i want to state that i have some knowledge of the legal issues concerning changing of MAC addresses and the sole reason that i want to do this is because privacy is a big issue for me and i have a right to enjoy my right. Therefore, any posts or argument concerning such are requested to be posted elsewhere where the topic expressly states so.
Also, please treat me like a newbie when it comes to developing and programming of any kind. I have a very shallow understanding of kernel and the likes.
I am using a rooted S5 G-900H(Exynos with BCM 4534 chip)
Running on 4.4.2 Kitkat stock ROM and Kernel
So without further ado, here is what i have found so far
The MAC address is reflected in a hidden file called .mac.info in the /efs/wifi/ folder. However, editing the file does not change the actual MAC address in anyway. A phone reboot or even turning the wifi on/off will just change it back to the original.
I dumped partitions from /dev/block/ on to my SD card and copied it to my laptop. I searched through the files and found the MAC address in the efs.img partition.My wifi was turned off and the plane was in airplane mode. I modified it and flashed it back using the dd command from terminal emulator on my phone(this can also be done through adb shell but im guessing if you know what that is then you obviously know how to do it).
I rebooted the phone and everything seemed fine. The Wifi MAC address in the status screen in settings displayed my edited address. The .mac.info file also displayed the same. The problem is that it reverted back to the original as soon as i turned on the wifi. The MAC address values in the .mac.info file, status screen and the efs partition from the /dev/block/, all changed back to the original.
I have read that for most phones the important information unique to that particular phone(like IMEI, wifi/BT MAC address, unlock codes and so on) is stored in the NV_DATA.bin file, but everything is encrypted. Also there are only guides as to searching unlock codes and such, so i tried to search for hash blocks randomly using Hex Editor but there was nothing of the sort and the only hash block i can recognize is the one with AES-Encryption as shown from another forum on this site.Maybe it is another type of encryption, but that was another dead end for me.
Then i tried to search and edit various files and kernels as such, but there are no kernels that directly offer this customization. Tried to edit init.tuna.rc but there was no such file in the root directory. Searched init.goldfish.rc and init.wifi.rc and found nothing, but i did see init.svc.macloader mentioned and since i didnt want to mess with programs in the /system/bin/file i left it as is.
Also tried to search through PARAM partition using Hex Editor but nothing was there. Did the same for RADIO and BOOT but i dont think i did find anything major there.
tried to edit /sys/class/net/wlan0/address but it didnt let me, even though i was mounted as r/w. Flashing through dd command on terminal also resulted in permission denied. I was only able to view or dump it. I thought that may have been the source, but modifying the MAC address through the busybox if config command was reflected on the file. which obviously means that its not.
Looked through the dmesg (kernel) log and found a few interesting things but i dont know how to interpret them and what to do with it either. Ill post it later.
There is no NVRAM.txt the only ones in place of it i have are nvram_mfg.txt, nvram_mfg.txt_wisol, nvram_mfg.txt_semco3rd, nvram_net.txt, nvram_net.txt_semco3rd, nvram_net.txt_wisol.
I did do a bit more searching and editing, but i dont recall them right now.
Now, After all that what i think is this.
There is a source for the original MAC address somewhere either hardcoded in the Broadcom chip or somewhere in the partitions under a layer of encyrption.
The Original MAC address is only accessed when the wifi is turned on and not on reboot. This means it is not in any file, program or script that activates on boot, so only scripts and files accessed and imported during the turning on of wifi
must have it. Also while wifi is on and running, busybox ifconfig command changes the MAC address succesfully albeit temporarily, although the change is not seen on the status screen and but it does on the .mac.info file.
Any help from anyone, especially from developers with knowledge of Android kitkat ROm and kernels would be very much appreciated.
Alpaca_Bandit said:
Hi,
First off i want to state that i have some knowledge of the legal issues concerning changing of MAC addresses and the sole reason that i want to do this is because privacy is a big issue for me and i have a right to enjoy my right. Therefore, any posts or argument concerning such are requested to be posted elsewhere where the topic expressly states so.
Also, please treat me like a newbie when it comes to developing and programming of any kind. I have a very shallow understanding of kernel and the likes.
I am using a rooted S5 G-900H(Exynos with BCM 4534 chip)
Running on 4.4.2 Kitkat stock ROM and Kernel
So without further ado, here is what i have found so far
The MAC address is reflected in a hidden file called .mac.info in the /efs/wifi/ folder. However, editing the file does not change the actual MAC address in anyway. A phone reboot or even turning the wifi on/off will just change it back to the original.
I dumped partitions from /dev/block/ on to my SD card and copied it to my laptop. I searched through the files and found the MAC address in the efs.img partition.My wifi was turned off and the plane was in airplane mode. I modified it and flashed it back using the dd command from terminal emulator on my phone(this can also be done through adb shell but im guessing if you know what that is then you obviously know how to do it).
I rebooted the phone and everything seemed fine. The Wifi MAC address in the status screen in settings displayed my edited address. The .mac.info file also displayed the same. The problem is that it reverted back to the original as soon as i turned on the wifi. The MAC address values in the .mac.info file, status screen and the efs partition from the /dev/block/, all changed back to the original.
I have read that for most phones the important information unique to that particular phone(like IMEI, wifi/BT MAC address, unlock codes and so on) is stored in the NV_DATA.bin file, but everything is encrypted. Also there are only guides as to searching unlock codes and such, so i tried to search for hash blocks randomly using Hex Editor but there was nothing of the sort and the only hash block i can recognize is the one with AES-Encryption as shown from another forum on this site.Maybe it is another type of encryption, but that was another dead end for me.
Then i tried to search and edit various files and kernels as such, but there are no kernels that directly offer this customization. Tried to edit init.tuna.rc but there was no such file in the root directory. Searched init.goldfish.rc and init.wifi.rc and found nothing, but i did see init.svc.macloader mentioned and since i didnt want to mess with programs in the /system/bin/file i left it as is.
Also tried to search through PARAM partition using Hex Editor but nothing was there. Did the same for RADIO and BOOT but i dont think i did find anything major there.
tried to edit /sys/class/net/wlan0/address but it didnt let me, even though i was mounted as r/w. Flashing through dd command on terminal also resulted in permission denied. I was only able to view or dump it. I thought that may have been the source, but modifying the MAC address through the busybox if config command was reflected on the file. which obviously means that its not.
Looked through the dmesg (kernel) log and found a few interesting things but i dont know how to interpret them and what to do with it either. Ill post it later.
There is no NVRAM.txt the only ones in place of it i have are nvram_mfg.txt, nvram_mfg.txt_wisol, nvram_mfg.txt_semco3rd, nvram_net.txt, nvram_net.txt_semco3rd, nvram_net.txt_wisol.
I did do a bit more searching and editing, but i dont recall them right now.
Now, After all that what i think is this.
There is a source for the original MAC address somewhere either hardcoded in the Broadcom chip or somewhere in the partitions under a layer of encyrption.
The Original MAC address is only accessed when the wifi is turned on and not on reboot. This means it is not in any file, program or script that activates on boot, so only scripts and files accessed and imported during the turning on of wifi
must have it. Also while wifi is on and running, busybox ifconfig command changes the MAC address succesfully albeit temporarily, although the change is not seen on the status screen and but it does on the .mac.info file.
Any help from anyone, especially from developers with knowledge of Android kitkat ROm and kernels would be very much appreciated.
Click to expand...
Click to collapse
As you said, ifconfig changes it, there are several apps that do it for you as well, chainfire also released a mac randomizer app. You also noted it's hardwired in, so i would just have a startup script that changes it if i were you, there night be a better way to do it though.
Sent from my Tw5ted SM-G900A using Tapatalk
Yes, I have been using pry-fi as an option but the thing is that when i'm watching videos or downloading large sized files from playstore or other file hosting sites, it starts to turn my wifi on/off several times before becoming stable and logging in to the AP again. I have tried macchanger also and both misbehave after an interval of time. Thats why im trying to search for a more cleaner way to do it.
Running an init script would be nice but i have no idea how to do that. But there should be a script that only runs when turning on the wifi right? Would you know where this file was located and how to modify it? and if so please tell me.
Alpaca_Bandit said:
Yes, I have been using pry-fi as an option but the thing is that when i'm watching videos or downloading large sized files from playstore or other file hosting sites, it starts to turn my wifi on/off several times before becoming stable and logging in to the AP again. I have tried macchanger also and both misbehave after an interval of time. Thats why im trying to search for a more cleaner way to do it.
Running an init script would be nice but i have no idea how to do that. But there should be a script that only runs when turning on the wifi right? Would you know where this file was located and how to modify it? and if so please tell me.
Click to expand...
Click to collapse
You can just use init.d to make the script, shell scripting isnt very hard and i won't give you a tutorial here. Also as noted many places when researchng changing a mac on android, you can't connect to secured APs, or it won't be easy at least. As i said before, there may be a better way to do this, but i do not know it.
Sent from my Tw5ted SM-G900A using Tapatalk
Ok, thanks a lot. Running a script might just be cleaner than anything else I have right now. I'll still be on the lookout for other ways though. Call me hard to please.
Btw, I think the reason most custom MAC addresses(if they do get changed) are too different than the ones registered on the chip. I've found that changing only the 2nd digit out of the 12 in the address, to an even hexadecimal number like 2 or A, works for me on my pc.
Also you need to forget the networks on your pc or android as soon as you change it. Doesnt matter if you have the password or not, it doesnt connect. Must be something to do with the saved info about the ap on the phone that messes it up.
Alpaca_Bandit said:
Ok, thanks a lot. Running a script might just be cleaner than anything else I have right now. I'll still be on the lookout for other ways though. Call me hard to please.
Btw, I think the reason most custom MAC addresses(if they do get changed) are too different than the ones registered on the chip. I've found that changing only the 2nd digit out of the 12 in the address, to an even hexadecimal number like 2 or A, works for me on my pc.
Also you need to forget the networks on your pc or android as soon as you change it. Doesnt matter if you have the password or not, it doesnt connect. Must be something to do with the saved info about the ap on the phone that messes it up.
Click to expand...
Click to collapse
I know on for example ddwrr and even some official router firmwares they allow you to spoof your mac, may be worth looking into how they do it, but i have a suspicion it might be done with a script.
Sent from my Tw5ted SM-G900A using Tapatalk
Hard Wired?
I have been messing with 2 Alcatel Ideal 4060a, (because I bricked the first one i had).
After bricking the first 4060a I had, (wiping all partitions), I bought a second, (so I could install TWRP on it back it up and restore the backup onto the first).
After Restoring the backup of the second onto the first, all was good until I tried to get them online together.
When one connected it knocked the other offline, because they both share the same MAC address.
This is my problem and I wish the Mac Addresses were hard wired, then i wouldn't have this problem.
This is good news for anyone who wants to know if mac addresses are indeed hard wired. They are not, (at least not in the 4060a).
Hope This Helps.
gscripting
MAC for bt and wifi reside in the EEPROM or NVRAM. And that is not editable.
To put it simply you can't change it. Only spoof it. And if you know it's not legal you probably shouldn't be asking.
Reported Is different from original
gscripting said:
I have been messing with 2 Alcatel Ideal 4060a, (because I bricked the first one i had).
After bricking the first 4060a I had, (wiping all partitions), I bought a second, (so I could install TWRP on it back it up and restore the backup onto the first).
After Restoring the backup of the second onto the first, all was good until I tried to get them online together.
When one connected it knocked the other offline, because they both share the same MAC address.
This is my problem and I wish the Mac Addresses were hard wired, then i wouldn't have this problem.
This is good news for anyone who wants to know if mac addresses are indeed hard wired. They are not, (at least not in the 4060a).
Hope This Helps.
gscripting
Click to expand...
Click to collapse
More info relative to these 2 phones
I installed an app called Change my Mac.
It Lists:
Original MAC 12:34:56:78:90:ab
Current MAC ff:ee:dd:cc:bb:aa
They Are Different.
I thought the original MAC address it's showing, was the one written in the EEPROM or NVRAM,
but it turns out, after installing Change My MAC on the other phone also, its lists the same Original and Current MAC addresses as the first phone.
The Current MAC address listed is the one reported in settings and my network.
I Use Change My MAC to set the reported MAC to the original every time the phone boots using Tasker on only one of them.
Using Change My MAC, the change lasts til boot.
Just passing it on for those that might be interested.
When I get link privileges, I'll add a screenshot of Change My MAC.
gscripting
I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
sinlog said:
I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
Click to expand...
Click to collapse
That backup is too large, I think. Should be more in the neighborhood of 250 MB? Have you tried the factory re-image where you just see the booting up screen and then hold down the two bottom hardware buttons until you get a prompt?
It's difficult--but not impossible--to damage the factory image unless you've been messing with the partitions. If that method does not get you there, consider making a NookManager card and trying to access the re-image routine from its menu.
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
sinlog said:
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
Click to expand...
Click to collapse
5 seconds is not enough time for NookManager to correctly make a backup. And, backups can only be seen on the card if you connect your NSTG to your PC while NookManager is running. Otherwise the partition is invisible.
It's hard to know since I have no experience with the NSTG. If it were an NST I would suggest that you perform the region change flash, but it's not clear if that will remove your light function or, indeed, if the flash is deep enough to rewrite the areas of your device that appear to be preventing boot. AFAIK there are no ROM images for the NSTG available. But there might be. Somewhere.
I guess if you have exhausted all the possibilities, rather than trashing the device I would try the region change (just flash the US firmware again--I assume that's what's on there already). It may or may not preserve the glowlight capability, but it might at least produce a functioning e-reader. But only as a last resort.
Edit: Hmm.... seems like I've been down this winding road before: https://forum.xda-developers.com/showpost.php?p=72551413&postcount=57
But I emphasize that this process worked for a plain NST, not the NSTG, so it is an absolute last resort (and might not work anyway because you could have a completely different situation). Next thing is to look at the innards of the 1.1 updater and see if Glowlight updates could be substituted...
O.K. So here is a thread that contains a link to an NSTG image and the instructions to write to your device (read down in the thread).
https://forum.xda-developers.com/showthread.php?t=2608815
What "may" happen: your device could end up with a mismatched serial number and or MAC address depending on how this image was made. There is information on this forum for correcting the MAC address. Just a disclaimer. I don't know. IF this is successful, you can then do a manual update to 1.2.2 and then root with the updated NookManager. I've checked the link to the image and it is still good. I got a file that is about 245 MB--seems about right. Presumably you use the image in place of your backup in the restoring process described in the thread.
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
sinlog said:
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
Click to expand...
Click to collapse
Oy.
I didn't think you would act so rashly with all my disclaimers. Well, it's done. I actually don't think the MAC address is a big deal unless you begin to have issues.
Did you actually manage to register? If so then the serial number must not currently be in use and the change you effected was deep enough to pass muster. If not....well battery life is said to be shorter for devices that have skipped registration.
Correcting the MAC address is described (sort of) here: https://forum.xda-developers.com/showthread.php?t=1483600
As far as I can guess it involves editing a hex file. Doable, but maybe not needed. There is no way to correct the serial number. It is heavily encrypted with private keys. Again, if you managed to register then this is all moot.
How are you judging lack of internet connectivity?
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
sinlog said:
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
Click to expand...
Click to collapse
You didn't answer my question about connectivity. Are you not able to make a connection? With only the stock device there is nothing to connect to other than B&N. What does it say about "Owner" in the Settings?
Yes, you should root. Be sure to use the NookManager update or it won't work.
Before we even think about the MAC address issue you need root access and some way to tell if you actually have an internet connection. That means some kind of functioning browser, etc.
Do you still have that weird backup? If so, keep it safe somewhere. You may want that someday.
I tried to download a book and I got this : Unable to download, Internal error...
I can ping the nook from the computer.
I will look into rooting the device in 2 or 3 hours and then post again. I suppose this is what you're referring to :
https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Thank you for your patience with me.
sinlog said:
I tried to download a book and I got this : Unable to download, Internal error...
Click to expand...
Click to collapse
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
nmyshkin said:
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
Click to expand...
Click to collapse
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
sinlog said:
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
Click to expand...
Click to collapse
Hmm... I'm surprised there are any books populating that section at all since the device is not registered. In any case, that is no test of connectivity since without registration the NSTG will spit out all kinds of generic messages about connections and failures if you attempt anything that requires access of B&N servers--like buying/downloading a book (which you can't do unless you are registered).
Rooted with nookManager updated. Opera mobile needs to be reinstalled. I can connect to the computer using es file explorer, so wifi is ok. BUT I can't use nookManager because I can't read the icon labels. I'll restore the backup tomorrow and I will try another rooting method. There are 2 more, I think : tiny and glownooter. Are there others ?
sinlog said:
BUT I can't use nookManager because I can't read the icon labels.
Click to expand...
Click to collapse
? Do you mean ADW Launcher? You can fix the icon label issue in the Settings. As I recall the default font color is white. That needs to be changed to black. The size can also be changed. Depending on what icon style you pick the label will either be on one line or, if longer, on two. LOTS of Settings in ADW. Don't write it off without spending some time working with it.
Sorry, I used glownooter. It's a lot like touchnooter, with which I am familiar. I still have to sign in to my google account and to install opera mobile. I'll be back when finished.
Opera mobile is installed and working. I still can't sign in to google but I can use yalp store and that's good. Thanks again, nmyshkin, you saved my nook glowlight.
OK, so I had a good idea, and did it badly...
I have a many-years old Nook Simple Touch (NST1 hereafter), which I had partitioned for more space to sideload. I decided a while back to simply load everything on a micro-SD card, which I did. I started having issues with NST1, so I purchased another (refurbed) Nook Simple Touch (NST2 hereatfer). I started looking for the info to undo the partitioning change, and came across info to backup and restore that involved deleting the partitions, and thus the restore process would rewrite them.
AH HAH! So, I figured I could backup the NST2, which was fresh, and restore it to NST1. Worked like a charm, too.
Now we come to the problem... It also overwrote both the serial number, which I have no way to get back that I can find, and overwrote the MAC address of NST1. The original MAC address I do have, if I knew where to put it. And, if there's a way to find the original serial number, that too would be good to put back.
So, there you have it. Anybody got any ideas? I'm sure someone, probably many someones here, know where this data is recorded on the NST, and the easiest way to modify the data so it reflects the original information. I'm also hoping that someone can give me ideas on how to find the original serial number again. (Yes, I know it is written on the case where the micro-SD card goes in, but over the years that has become mostly unreadable, so that's out.)
Thanks muchly for any help you can offer,
MildBill
MildBill said:
OK, so I had a good idea, and did it badly...
I have a many-years old Nook Simple Touch (NST1 hereafter), which I had partitioned for more space to sideload. I decided a while back to simply load everything on a micro-SD card, which I did. I started having issues with NST1, so I purchased another (refurbed) Nook Simple Touch (NST2 hereatfer). I started looking for the info to undo the partitioning change, and came across info to backup and restore that involved deleting the partitions, and thus the restore process would rewrite them.
AH HAH! So, I figured I could backup the NST2, which was fresh, and restore it to NST1. Worked like a charm, too.
Now we come to the problem... It also overwrote both the serial number, which I have no way to get back that I can find, and overwrote the MAC address of NST1. The original MAC address I do have, if I knew where to put it. And, if there's a way to find the original serial number, that too would be good to put back.
So, there you have it. Anybody got any ideas? I'm sure someone, probably many someones here, know where this data is recorded on the NST, and the easiest way to modify the data so it reflects the original information. I'm also hoping that someone can give me ideas on how to find the original serial number again. (Yes, I know it is written on the case where the micro-SD card goes in, but over the years that has become mostly unreadable, so that's out.)
Thanks muchly for any help you can offer,
MildBill
Click to expand...
Click to collapse
You can find the serial number on the edge of the NST, hidden behind the SD card "door".
As to the rest, you may be SOL. There are places on the device where the S/N and MAC address are stored as strings, but I think the actual information is stored more deeply and may be encrypted with keys. Still, can't hurt to scour the forum. I could be wrong.
nmyshkin said:
You can find the serial number on the edge of the NST, hidden behind the SD card "door".
Click to expand...
Click to collapse
As I stated in the OP, that data is no longer readable, after many years of use. I have the MAC address (did you *read* the post??) I need to know where to put it!
MildBill said:
As I stated in the OP, that data is no longer readable, after many years of use. I have the MAC address (did you *read* the post??) I need to know where to put it!
Click to expand...
Click to collapse
Yeah, I missed that last part. Search on "serial number" and you'll find a dev discussion about this. Unless you have a copy of the original ROM partition I don't think you can do anything.
nmyshkin said:
Yeah, I missed that last part. Search on "serial number" and you'll find a dev discussion about this. Unless you have a copy of the original ROM partition I don't think you can do anything.
Click to expand...
Click to collapse
Surely there is some way to insert/change the existing data to reflect the original. And, no, sadly, stupidly, I did not back up that data, I had forgotten it was coded in flash, and knew I was going to overwrite the entire device.
It's been a while since I worked on NSTs.
On the iMX6 (Glows), the serial number is in two places:
In mmcblk0 at offset 200 it says "SN-12345667890123456", I believe purely as informational.
In mmcblk0 at offset 80400 is an XML structure with the SN used by Android.
On the OMAP3 (NST), the serial number is in two places:
/rom/devconf/DeviceID (16 bytes ASCII)
/rom/devconf/SerialNumber (16 bytes ASCII)
/rom is normally mounted r/w so you can just write these and reboot.
Renate NST said:
It's been a while since I worked on NSTs.
On the OMAP3 (NST), the serial number is in two places:
/rom/devconf/DeviceID (16 bytes ASCII)
/rom/devconf/SerialNumber (16 bytes ASCII)
/rom is normally mounted r/w so you can just write these and reboot.
Click to expand...
Click to collapse
Bless you Renate, I knew you would know! How about the location of the MAC address?? This appears to also be software coded somewhere, as when I was finished with the process outlined above, both devices have the same MAC address.
MildBill said:
How about the location of the MAC address?
Click to expand...
Click to collapse
Code:
# cd /rom/devconf
# echo -n 1234567890123456 > DeviceID
# echo -n 1234567890123456 > SerialNumber
# echo -n 123456789012 > MACAddress
Renate NST said:
Code:
# cd /rom/devconf
# echo -n 1234567890123456 > DeviceID
# echo -n 1234567890123456 > SerialNumber
# echo -n 123456789012 > MACAddress
Click to expand...
Click to collapse
Renate,
Yes, I have successfully deciphered (mostly) the serial number/device ID printed on the case near the micro-SD slot. I had to guess a couple of numbers but I think I got them right.
And, I saw the MAC address file as pointed out, BUT, I changed that as well, maintaining the format involved, and when restarted the device info said 'Unavailable' for the MAC address, until I turned WiFi on, and then that reverted to the wrong address, as written from the other device. I'm assuming that there is some other place where it is stored in some form. Any ideas on that?
MildBill
P.S. Actually, I edited the files with a Windows editor, the serial/device ID change worked fine as far as I can see.
P.P.S. On further check, while the Device Info:About Your Nook shows the 'cloned' MAC address after turning WiFi on, the MAC Address file still reflects the original address (obtained from a separate source from prior to the whole business.
Read this thread
https://forum.xda-developers.com/showthread.php?t=1480974
Yeah, the initialization of the WiFi adapter is in /rom/devconf/WiFiBackupCalibration.
It's a series of register addresses/counts and data.
The MAC is in reverse order in hex, not ASCII.
Code:
0x00 - 0x01
0x01 - 0x6d
0x02 - 0x54
0x03 - 6th byte MAC
0x04 - 5th byte MAC
0x05 - 4th byte MAC
0x06 - 3rd byte MAC
0x07 - 0x01
0x08 - 0x71
0x09 - 0x54
0x0a - 2nd byte MAC
0x0b - 1st byte MAC
OK, I have decided to change directions...
After getting all the data changed, I tried to erase and deregister, then register again, and it gives me errors.
All the data, by the way, as well as the Main Board SN are on a sticker ON the motherboard, so I know I got them right. There are, however other bits of data not there, which no doubt need to all match up, and don't. So, I have decided this can be a test device for some of the various rooted ROMs, and other goodies out there, to see if any of them are worthwhile to use. If not, I will simple restore the NST2 backup to it, and simply make sure I don't have both of them powered up and online at the same time.
Thanks to all for trying to help, even if it didn't work out. The new (to me) device will last me for many more years I'm sure.
MildBill
MildBill said:
OK, I have decided to change directions...
After getting all the data changed, I tried to erase and deregister, then register again, and it gives me errors.
All the data, by the way, as well as the Main Board SN are on a sticker ON the motherboard, so I know I got them right. There are, however other bits of data not there, which no doubt need to all match up, and don't. So, I have decided this can be a test device for some of the various rooted ROMs, and other goodies out there, to see if any of them are worthwhile to use. If not, I will simple restore the NST2 backup to it, and simply make sure I don't have both of them powered up and online at the same time.
Thanks to all for trying to help, even if it didn't work out. The new (to me) device will last me for many more years I'm sure.
MildBill
Click to expand...
Click to collapse
Yes, I'm sure you noticed in the link I posted above that you will not be able to register the device. The original info is stored and processed with keys and these are used when communicating with B&N.
You may have missed the link within the link: http://forum.xda-developers.com/showthread.php?t=892426
This may allow you to fix the MAC address issue. Seems to have worked for others.
So the really big issue is then how to overcome the rapid battery drain of an unregistered NST. I tried many things when I got my second NST but was never able to find something that didn't just make things worse. A truly B&N-free NST is a really worthy goal, but only if the battery issue can be solved. It seems like every attempt to disable/delete parts of the B&N system sets up a constantly running panic in the system background. The same appears to be true if you skip OOBE.
Advice: do a reset, try the MAC fix. If it works, do a backup. That's your baseline.
Good luck.
Edit: I can confirm that the method described in the link above does seem to successfully spoof the MAC address, as least as far as my router is concerned. I used an online hex editor to make the changes on a copy of the /rom/devconf/WiFiBackupCalibration file and then copied it back to my NST and rebooted. Initially in my Nook Settings app the MAC address shows up as "unknown", but this seems to be true at every reboot. Once a WiFi connection is made, the spoofed address is shown by the router and it even shows up in the Settings app thereafter without any additional changes.