Hello.
I used the ubuntu restore from AdamOutler. It worked like a charm to restore my borked Nook tablet. But for what ever reason it picked up a serial number that doesnt match the one that is registered to me and my tablet. Is there a adb command or something along those lines that i can restore my serial with? I changed the serials via root explorer but it always defaults back to the wrong serial. I know it must be something I did along the line of trying to fix it but it bothers me it doesnt match to my account. It wont let me register it again. Thank you for any help...
markbird1 said:
Hello.
I used the ubuntu restore from AdamOutler. It worked like a charm to restore my borked Nook tablet. But for what ever reason it picked up a serial number that doesnt match the one that is registered to me and my tablet. Is there a adb command or something along those lines that i can restore my serial with? I changed the serials via root explorer but it always defaults back to the wrong serial. I know it must be something I did along the line of trying to fix it but it bothers me it doesnt match to my account. It wont let me register it again. Thank you for any help...
Click to expand...
Click to collapse
Since no one has answered I'll give it a try. The place I find the serial number is
/rom/devconf/SerialNumber it is 16 bytes and permissions are r--r----- or
440. Since you didn't say where you were making the change this may not help.
also for info you will find /system/xbin/setserial hope this limited info may help.
Good luck!
Forgot something. I believe you can register multiple devices with google and use the same account. Mine is registered two different ways. I am registered as
Bn Nook Tablet
and
Barnes&Noble BNTV250
both are the same unit just different builds.
I'm glad im not the only one that this happen to there nook.
i sent Adam a PM last week about it and he told me that he will be making an app for that so let's hope he didn't forget.
In the mean time any help will be greatly appreciated.
Hello again,
I found two places where the serial is stored both in the rom folder. One is the "Serialnumber" file and the other is label "deviceID". Changing both will not outlast a system reset. There must be a hidden backup file where this number is stored also.
markbird1 said:
Hello again,
I found two places where the serial is stored both in the rom folder. One is the "Serialnumber" file and the other is label "deviceID". Changing both will not outlast a system reset. There must be a hidden backup file where this number is stored also.
Click to expand...
Click to collapse
Interesting!
serial number change
The same thing happened to me. Please prod Adam to make that app or post any other solution that is found!
no news yet =/
Any solution yet ??
sailerph said:
Any solution yet ??
Click to expand...
Click to collapse
Try this link.
http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
tobdaryl said:
Try this link.
http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
Click to expand...
Click to collapse
I tried this method, but for some reason, I kept getting errors when trying to write from the unmounted SD card with DD, and, when trying with the device mounted, it would continue to write the .img file, (3-4 gig before I realized why it was taking so long.)
However, once I had the "ROM" sd card, and modified the files as necessary, I booted a CM7 SD card with my nook, installed one of the many "Root" filesystem managers, and replaced the edited DeviceID and SerialNumber files on my Nook's internal ROM.
This worked -- to an extent. B&N's default software now shows my proper Serial #, however, my B&N will still not pass registration.
I'm thinking that perhaps there's something more to the registration process, MAC address perhaps?
((UPDATE))
So, I took the plunge, cracked open the back of the nook, and found the MAC address on a sticker inside, handy that, eh?
However - This still will not pass B&N registration, so there's something that I've managed to mess up beyond that. I'm guessing this particular NT will never be able to use stock ROM's again. Oh, well, not a huge loss IMHO.
((END UPDATE))
I'm probably not going to poke at it further, as I dont acutally plan on using B&N's default software, I purchased my NT with the express intention of rooting. My only worry is warranty, however, I purchased the Best Buy "Accidental Damage" warrenty, so, if it does break. I just need to "drop" it so the screen cracks! LOL!
Nook Tablet Serial Number Restore & MAC Address restore
Thanks to all for the help with repartitioning/rebuilding Nook Tablet. Here's my input to help others on their way.
Serial Number and MAC Address restore.
You will need to install a hex editor to your laptop - one like "Free Hex Editor Neo".
We will find every instance of the serial Number and of the Mac Address in Partition 5 and change them to the correct values.
This also will automatically correct the DeviceID.
Write down your incorrect values and your correct values for Serial Number and MAC Address
Now we will modify an existing rom image for Partition 5
-if you have an existing image for Partition 5 in your laptop make a copy of it and put it in C:/download.
. -skip to step 9
-otherwise do the following:
Get the image for partition 5 from your Nook Tablet and copy it to your laptop.
1. adb shell
2. ~# mount sdcard
3. ~# dd if=/dev/block/mmcblk0p5 of=/sdcard/blk/mmcblk0p5.img
..-this copied the rom image to the sd card. It is about 48MB.
4. ~# exit
5. cd /
6. adb pull /sdcard/blk/mmcblk0p5.img /download/mmcblk0p5.img
..-this copies the image file from the SD card to your laptop. Places it in the C:/download subdirectory.
7. adb shell
8. rm /sdcard/blk/mmcblk0p5.img
..-this deletes the image file from the SD card
Edit the image file
9. Open Free Hex Editor Neo
.......-file, open file, C:\download\mmcblk0p5.img
10. Search for the old incorrect value for the serial number
11. click on the right side of the hex editor (on the ansi script)
.......-do a replace
...............-type in correct serial number
...............-replace every instance of the serial number in the file
12. Do the same operation to find/replace the MAC address
13. save the file. remove the “.img” file extension from it.
14. put it on the sd card in the root directory (either push it or place the SD card in your laptop)
15. adb shell
16. ~# mount sdcard
17. ~# dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5
18. ~# exit
19. remove sdcard, reboot internal.
Cheers.
markbird1 said:
Hello.
I used the ubuntu restore from AdamOutler. It worked like a charm to restore my borked Nook tablet. But for what ever reason it picked up a serial number that doesnt match the one that is registered to me and my tablet. Is there a adb command or something along those lines that i can restore my serial with? I changed the serials via root explorer but it always defaults back to the wrong serial. I know it must be something I did along the line of trying to fix it but it bothers me it doesnt match to my account. It wont let me register it again. Thank you for any help...
Click to expand...
Click to collapse
Do you have the serial number, and mac address that it changed yours to?
Related
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
Has anyone found a method for restoring Serial Number and DeviceID after recovering a bricked NT? I've recovered, but I can't re-register with B&N due to missing SN/ID? Not really finding any answers in the forums so far. If you have some info or can point me in the right direction, I'd be greatful. (yes I have been trying to look through the forums, just not seeing an answer, though it seems many have asked).
shawnshine2 said:
Has anyone found a method for restoring Serial Number and DeviceID after recovering a bricked NT? I've recovered, but I can't re-register with B&N due to missing SN/ID? Not really finding any answers in the forums so far. If you have some info or can point me in the right direction, I'd be greatful. (yes I have been trying to look through the forums, just not seeing an answer, though it seems many have asked).
Click to expand...
Click to collapse
I would have expected a deregister and reset would have restored your sn.
Beyond that I have found the sn at two locations.
/rom/devconf/SerialNumber
/rom/devconf/DeviceID
these are both text files; there may be others but this is what I found
your sn is located where your sdcard plugs in if you don't have it otherwise
I have not tried to edit these files so I can't suggest you do.
Sorry not much help but that's all I have.
I lost mine once but it returned after I replaced the restore partition and did a reset.
added info:
I pulled both files listed above and checked them with a hex editor and they contain the sn and only the sn - no extra characters of any kind (16 bytes only) permissions on are 440 and 440.
Thanks for the bit o' info. Unfortunately it's not as simple as that. The entire partition table had been deleted thus removing all of the data for the NT. I was able to recreate the partitions, and using meghd00t's & CRE's recovery method got v.1.4.0 B&N reinstalled. Now I'm not able to re-register the device with B&N due to missing DeviceID/Serial. I'm still looking around seeing if I can find a way to re-enter the info. I haven't had much luck in finding an easy way to do it, much less a hard way.
Serial number resolved / Now need Model Number & MAC location
It looks like I only had one file "/rom/devconf/DeviceID" that was only 8 zeros. I pulled the file with ADB, added my SN, saved and pushed it back. I took the saved file, renamed it to SerialNumber and did a push to rom as well.
C:\android-sdk-windows\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb pull /rom/devconf/DeviceID
1 KB/s (8 bytes in 0.007s)
(here I pulled the file: notice it's only 8bytes instead of 16. Once I had the file my pc, I edited it with Notepad and added my 16digit serial, then saved)
C:\android-sdk-windows\platform-tools>adb push DeviceID /rom/devconf
2 KB/s (16 bytes in 0.007s)
(here I pushed the file back to the nook. notice it is now 16bytes)
C:\android-sdk-windows\platform-tools>adb push SerialNumber /rom/devconf
3 KB/s (16 bytes in 0.004s)
(here I renamed the file on my pc as SerialNumber then pushed it to the rom)
C:\android-sdk-windows\platform-tools>adb shell
~ # ls
ls
boot etc sd-ext
bootdata init sdcard
cache init.rc sys
data proc system
datadata res tmp
default.prop rom ueventd.acclaim.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd rom
cd rom
/rom # cd devconf
cd devconf
/rom/devconf # ls
ls
DeviceID SerialNumber
/rom/devconf # cat DeviceID
cat DeviceID
20202400########/rom/devconf #
/rom/devconf # cat SerialNumber
cat SerialNumber
20202400########/rom/devconf #
/rom/devconf # exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
C:\android-sdk-windows\platform-tools>
Now the Nook registers the Serial Number. What I need now is to find out where the MAC address and Model number should be listed (located). If I can get that added, I think I'll be good to go. At least I'm now half way there!
shawnshine2 said:
It looks like I only had one file "/rom/devconf/DeviceID" that was only 8 zeros. I pulled the file with ADB, added my SN, saved and pushed it back. I took the saved file, renamed it to SerialNumber and did a push to rom as well.
C:\android-sdk-windows\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb pull /rom/devconf/DeviceID
1 KB/s (8 bytes in 0.007s)
(here I pulled the file: notice it's only 8bytes instead of 16. Once I had the file my pc, I edited it with Notepad and added my 16digit serial, then saved)
C:\android-sdk-windows\platform-tools>adb push DeviceID /rom/devconf
2 KB/s (16 bytes in 0.007s)
(here I pushed the file back to the nook. notice it is now 16bytes)
C:\android-sdk-windows\platform-tools>adb push SerialNumber /rom/devconf
3 KB/s (16 bytes in 0.004s)
(here I renamed the file on my pc as SerialNumber then pushed it to the rom)
C:\android-sdk-windows\platform-tools>adb shell
~ # ls
ls
boot etc sd-ext
bootdata init sdcard
cache init.rc sys
data proc system
datadata res tmp
default.prop rom ueventd.acclaim.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd rom
cd rom
/rom # cd devconf
cd devconf
/rom/devconf # ls
ls
DeviceID SerialNumber
/rom/devconf # cat DeviceID
cat DeviceID
20202400########/rom/devconf #
/rom/devconf # cat SerialNumber
cat SerialNumber
20202400########/rom/devconf #
/rom/devconf # exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
C:\android-sdk-windows\platform-tools>
Now the Nook registers the Serial Number. What I need now is to find out where the MAC address and Model number should be listed (located). If I can get that added, I think I'll be good to go. At least I'm now half way there!
Click to expand...
Click to collapse
Hang in there, this can be done. With cwm I formatted everything including rom and I was able to recover. I'll check on mac and get back so just remain positive.
How to find your Original B&N Nook Tablet MAC Address
I don't know if there is a way to find the Nook Tablet's original MAC address using ADB, but as far as I could find, IF you had ever flashed a version of CM7 onto your device the MAC address is given as 08:00:28:12:03:58. So unless you wrote down your original MAC address before flashing, you will end up with this one. I however do remember a little trick with pc's. When you have a bad nic card in a pc and your dealing with Firewalls and Routers (as I do for work) you can open the system and find the MAC address either printed directly on the board or listed on a sticker that's attached. So I did a little bit of rummaging through some YouTube videos and found a tear down of the NT. Lo and behold, right inside the back cover is a sticker with the NT's serial number AND MAC address. The video for cracking open your nook is here: http://www.youtube.com/watch?v=3SVO2JCgqPM And the website for the tear down is here: http://www.ifixit.com/Teardown/Nook-Tablet-Teardown/7121/1
But, if you don't have a T5 torq's screwdriver to remove the two screws at the SDcard door, if you are very very very careful and gentle, you can still use a tiny (and I mean tiny) flat head and gently insert at the bottom of the back panel right at the middle point and gently pry the back off working your screwdriver in a clockwise direction. Just don't try to pop that lower right hand corner open, you will break the case. (you been warned). Once you have about 3 quarters of the back popped off gently lift up the back cover and peer inside, you should see the SN & MAC address label. Copy the numbers. Replacing the cover back you need to be just as gentle and you want to work it back in going in a counterclockwise motion and only use the screwdriver to help work the last one or two tabs back in. If you are careful enough you won't even know that it was ever open. NOTE: There are two tiny gray paper stickers over the two screws at the SDcard door. If you remove the two papers, and expose the screws, you may have a hard time getting warrenty work done. So just know that before you start futzing with it.
Now if I can just find out where the heck the MAC address is located in the B&N v.1.4.0 software.
shawnshine2 said:
It looks like I only had one file "/rom/devconf/DeviceID" that was only 8 zeros. I pulled the file with ADB, added my SN, saved and pushed it back. I took the saved file, renamed it to SerialNumber and did a push to rom as well.
C:\android-sdk-windows\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb pull /rom/devconf/DeviceID
1 KB/s (8 bytes in 0.007s)
(here I pulled the file: notice it's only 8bytes instead of 16. Once I had the file my pc, I edited it with Notepad and added my 16digit serial, then saved)
C:\android-sdk-windows\platform-tools>adb push DeviceID /rom/devconf
2 KB/s (16 bytes in 0.007s)
(here I pushed the file back to the nook. notice it is now 16bytes)
C:\android-sdk-windows\platform-tools>adb push SerialNumber /rom/devconf
3 KB/s (16 bytes in 0.004s)
(here I renamed the file on my pc as SerialNumber then pushed it to the rom)
C:\android-sdk-windows\platform-tools>adb shell
~ # ls
ls
boot etc sd-ext
bootdata init sdcard
cache init.rc sys
data proc system
datadata res tmp
default.prop rom ueventd.acclaim.rc
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cd rom
cd rom
/rom # cd devconf
cd devconf
/rom/devconf # ls
ls
DeviceID SerialNumber
/rom/devconf # cat DeviceID
cat DeviceID
20202400########/rom/devconf #
/rom/devconf # cat SerialNumber
cat SerialNumber
20202400########/rom/devconf #
/rom/devconf # exit
exit
C:\android-sdk-windows\platform-tools>adb kill-server
C:\android-sdk-windows\platform-tools>
Now the Nook registers the Serial Number. What I need now is to find out where the MAC address and Model number should be listed (located). If I can get that added, I think I'll be good to go. At least I'm now half way there!
Click to expand...
Click to collapse
I'm only finding the mac at one location (seems to easy) but that may be all.
/rom/devconf/MACAddress 12 bytes 440 permissions no colons used in this file just the address all typed together.
We must have been typing together. I run cm7 internal final and have my mac as from the factory. What you mentioned may have related to the first version.
I must have been asleep earlier. Model no
/rom/devconf/ModelNuumber 7 bytes permissions 440 - (BNTV250)
One more step done, another one pops up.
Add the files and I got that knocked out but still having an issue. My devconf directory only had the one original file. I've added the ones you listed and now I have the Serial, Model, and MAC all showing on the Device Info tab. I think there has to be a second MAC location as when I get the Wifi page of the setup screens, it's still listing the old bad MAC address. But It does let me connect to my router. But when it goes to register I still get the error screen. When I click Device Info button, it shows all my info in Green now, but shows Battery: ! 100% in red. I reset battery stats, but nothing changed. I'll keep cracking away at it.
shawnshine2 said:
Add the files and I got that knocked out but still having an issue. My devconf directory only had the one original file. I've added the ones you listed and now I have the Serial, Model, and MAC all showing on the Device Info tab. I think there has to be a second MAC location as when I get the Wifi page of the setup screens, it's still listing the old bad MAC address. But It does let me connect to my router. But when it goes to register I still get the error screen. When I click Device Info button, it shows all my info in Green now, but shows Battery: ! 100% in red. I reset battery stats, but nothing changed. I'll keep cracking away at it.
Click to expand...
Click to collapse
I'm getting a different sense of where we began than I was in the beginning. Are you running CM7 and if so is it from the sdcard?
As a note /rom/devconf includes seventeen files total in my configuration (cm7 alpha final internal - flashed from 1.4.0). If you are running cm7 from sdcard I'll restore to 1.4.0 and see if I can help from there.
Restored all the info / but I think it's a fruitless quest
Whole story long........ I started out with a Nook Tablet that had no partitions, I acquired it that way. It had nothing, wouldn't even boot up. So I have been playing with it for two weeks trying to get it unbricked. After many tries and countless hours, using adamoutler, veronica, and meghd00t & EMR's forum posts I was able to get it running with the SDcard (CM7). I had to recreate the partitions in ADB. I struggled with the whole boot w/wo usb cable & sdcard for a long time. Finally on Friday I used EMR's recovery image and got it where I could finally make some headway and was finally able to boot normally. I used the internal restore image that Veronica posted but was unable to register with B&N. Thus began the search for Serial Numbers & MAC Addresses. The funny thing about that image (and I don't know if it's just because I never had the files to begin with) when you had told me about all the files in /rom/devconf I was confused cause I had only the one empty file. I recreated the files you suggested but still couldn't register. So I went back to one of Veronica's other posts about restoring partition images using the dd command. I copied partition 5, 6, 7, 8, and 9 using her partition images and all of the missing information was restored. I just had to edit the SerialNumber, DeviceID, MACAddress file and I used xvi32 hex editor to add my original MAC address back into the WiFiBackupCalibration file. After all of that, I re-flashed the original recovery software and did a complete restore of the B&N software back to version 1.0.0 . I am sad to report that I am still unable to register it back with B&N. Not a really a big deal, I just wanted to see if I could get it back to as close to original as I could. Using the bypass registration technique shows that there are several additional individual "keys" (hash private key and public key)that are locked to the device from the factory (most likely to keep people from doing what we are doing) and if what is on the device doesn't match what they have in the system from the factory then it refuses the registration. (my theory anyway). So unless someone knows something I don't, that's what I'm going with. One thing I have noticed is that on the Registration Error page, just below the Device Info button is a code B-CM1004. I'm curious if that is an error code and if it is what it might mean? If I find anything else I'll post back. Moral of the story is that I've since flashed CM7 internally and I now have my original MAC address. (always a silver lining).
shawnshine2 said:
Whole story long........ I started out with a Nook Tablet that had no partitions, I acquired it that way. It had nothing, wouldn't even boot up. So I have been playing with it for two weeks trying to get it unbricked. After many tries and countless hours, using adamoutler, veronica, and meghd00t & EMR's forum posts I was able to get it running with the SDcard (CM7). I had to recreate the partitions in ADB. I struggled with the whole boot w/wo usb cable & sdcard for a long time. Finally on Friday I used EMR's recovery image and got it where I could finally make some headway and was finally able to boot normally. I used the internal restore image that Veronica posted but was unable to register with B&N. Thus began the search for Serial Numbers & MAC Addresses. The funny thing about that image (and I don't know if it's just because I never had the files to begin with) when you had told me about all the files in /rom/devconf I was confused cause I had only the one empty file. I recreated the files you suggested but still couldn't register. So I went back to one of Veronica's other posts about restoring partition images using the dd command. I copied partition 5, 6, 7, 8, and 9 using her partition images and all of the missing information was restored. I just had to edit the SerialNumber, DeviceID, MACAddress file and I used xvi32 hex editor to add my original MAC address back into the WiFiBackupCalibration file. After all of that, I re-flashed the original recovery software and did a complete restore of the B&N software back to version 1.0.0 . I am sad to report that I am still unable to register it back with B&N. Not a really a big deal, I just wanted to see if I could get it back to as close to original as I could. Using the bypass registration technique shows that there are several additional individual "keys" (hash private key and public key)that are locked to the device from the factory (most likely to keep people from doing what we are doing) and if what is on the device doesn't match what they have in the system from the factory then it refuses the registration. (my theory anyway). So unless someone knows something I don't, that's what I'm going with. One thing I have noticed is that on the Registration Error page, just below the Device Info button is a code B-CM1004. I'm curious if that is an error code and if it is what it might mean? If I find anything else I'll post back. Moral of the story is that I've since flashed CM7 internally and I now have my original MAC address. (always a silver lining).
Click to expand...
Click to collapse
I haven't abandoned your problem but from here it will be much slower to find a path unless someone with prior knowledge comments. In the meantime you may be able to register B&N from CM7 with NOOK for Android by B&N. https://play.google.com/store/search?q=nook&c=apps
I haven't made any progress toward clearing your problem. If it were mine I would think seriously about doing a CWM backup, doing this recovery “[UnBrick]TOTAL WIPE and reflash back to 1.4.0 via Ubuntu Recovery --Now Easier!!!!”.http://forum.xda-developers.com/showthread.php?t=1470910
Once that is completed reboot into recovery and allow stock 1.4.0 recovery. You could always restore your backup if this failed. If reluctant to try this then you can try NOOK for Android by B&N from Google Play(Android Market) and maybe get registered with your current setup.https://play.google.com/store/search?q=nook+for+android
I'm sorry but this is all I can formulate now.
You guys are way more knowledgeable than me, but, is it possible that you can't register your Tablet, shawnshine2, because the last owner didn't deregister it?
smarcin said:
You guys are way more knowledgeable than me, but, is it possible that you can't register your Tablet, shawnshine2, because the last owner didn't deregister it?
Click to expand...
Click to collapse
Of course it is possible. Thanks for replying 3 heads are better than 2.
I have a theory that I use to help keep me grounded so I can't agree that we know more.
Want to hear my theory? Well I'll tell you either way! I may know more about some subject but you will know more about others; it takes all of us to make the world a better place.
Thanks for your input and I'm throwing a thanks your way.
And finally the saga ends ...for better or worse.
So to give a final ( ? ) update here, after going through every forum post I could find and even trying a few things not covered I finally gave in and called customer support. Since I bought this used and completely wiped out, I didn't expect that they would be much help. I was surprised. The CSR asked a few questions about what the problem was and I give it to him straight. He was surprisingly understanding. He looked up the serial number and said it was still registered to the previous owner, but it was also still under warranty. Here he was little cautious with me, but I give him all of my buddies information, name, address, phone number, email. With that, he was a little more comfortable. He said that he needed to De-register it on their servers and then for me to try again in 15 minutes. Unfortunately, this did not fix it. I called him back and he passed me to the technical desk. They in-turn had me try to do a "hard reset" (as if I hadn't done that 100 times already). When that failed, he said that the only thing they could do was to swap it out. I figured they'd say no since I wasn't the original owner, but they actually went ahead and sent the email with the return voucher to my buddy. He was gracious enough to print it out for me. Went to the store later in the afternoon and they switched it out no questions asked with a cert. pre-owned. But in true sales-people style, they talked me into buying a new case! So, I am at a loss to say what the problem was but B&N really didn't seem to care. They just wanted to make sure I was happy with their customer service, which, at the end of the day, I am really grateful for. I'm sorry I don't have the answer that can solve this problem for others, but honesty with B&N at least got me a replacement with almost no hassle. So, if nothing else, you can always give that a shot.
shawnshine2 said:
So to give a final ( ? ) update here, after going through every forum post I could find and even trying a few things not covered I finally gave in and called customer support. Since I bought this used and completely wiped out, I didn't expect that they would be much help. I was surprised. The CSR asked a few questions about what the problem was and I give it to him straight. He was surprisingly understanding. He looked up the serial number and said it was still registered to the previous owner, but it was also still under warranty. Here he was little cautious with me, but I give him all of my buddies information, name, address, phone number, email. With that, he was a little more comfortable. He said that he needed to De-register it on their servers and then for me to try again in 15 minutes. Unfortunately, this did not fix it. I called him back and he passed me to the technical desk. They in-turn had me try to do a "hard reset" (as if I hadn't done that 100 times already). When that failed, he said that the only thing they could do was to swap it out. I figured they'd say no since I wasn't the original owner, but they actually went ahead and sent the email with the return voucher to my buddy. He was gracious enough to print it out for me. Went to the store later in the afternoon and they switched it out no questions asked with a cert. pre-owned. But in true sales-people style, they talked me into buying a new case! So, I am at a loss to say what the problem was but B&N really didn't seem to care. They just wanted to make sure I was happy with their customer service, which, at the end of the day, I am really grateful for. I'm sorry I don't have the answer that can solve this problem for others, but honesty with B&N at least got me a replacement with almost no hassle. So, if nothing else, you can always give that a shot.
Click to expand...
Click to collapse
Great! I'm glad you didn't wait any longer on me as I was stumped.
Happy computing.
Not wanting to give up but may have to
After hours and hours of searching and reading, I must say this post makes me kind of sad. I haven't taken the time to reset my serial number and MAC, but this post makes me think "why bother". I really love my Nook & I was trying to unRoot and just go back to stock. Somewhere along the way I must've clicked something wrong and hosed it all up. AdamOutler's Total Wipe method was the only thing I could find to get me out of a CWM bootloop. Mine is right at a year old (Christmas gift last year), so I seriously doubt B&N will be as forgiving with me.
Just adding to this thread in case someone has figured out anything since April. I also messaged Adam to see if he had any thoughts. Sadness is setting in.
Vol4Ever said:
After hours and hours of searching and reading, I must say this post makes me kind of sad. I haven't taken the time to reset my serial number and MAC, but this post makes me think "why bother". I really love my Nook & I was trying to unRoot and just go back to stock. Somewhere along the way I must've clicked something wrong and hosed it all up. AdamOutler's Total Wipe method was the only thing I could find to get me out of a CWM bootloop. Mine is right at a year old (Christmas gift last year), so I seriously doubt B&N will be as forgiving with me.
Just adding to this thread in case someone has figured out anything since April. I also messaged Adam to see if he had any thoughts. Sadness is setting in.
Click to expand...
Click to collapse
Have you looked at this thread?
Yes. Read in detail. It tells you how to retrieve serial number, but that apparently doesn't get you past the B&N checks that occur when setting up the tablet. It still locks up and gives the number to tech support. Without completing the activation step, you can't access the B&N store or your previously purchased content.
Vol4Ever said:
Yes. Read in detail. It tells you how to retrieve serial number, but that apparently doesn't get you past the B&N checks that occur when setting up the tablet. It still locks up and gives the number to tech support. Without completing the activation step, you can't access the B&N store or your previously purchased content.
Click to expand...
Click to collapse
My reading of that thread's first post is it's about how to put tablet's serial number (which can be found on the back of the micro-SD card slot cover) back into the NT's relevant system info files. The "Retrieve" word in the OP's thread title is, unfortunately, misleading.
Managed to fix my wifi mac address problem with some info read in this thread:
forum.xda-developers.com/showthread.php?t=1131649
all performed using linux,
connect phone to pc using in terminal
adb shell
dd if=/dev/block/mmcblk0p3 of=/sdcard/filename.img (stored image of block on sdcard)
exit
exit
disconnect then reconnect phone to pc this time allowing access to sdcard.
in terminal mount the image for editing
mount -o loop /source/filename.img /destination/
using a hex editor modify '/wifi/wlan_mac.bin' with wanted address
save
unmount /destination/
the filename.img has now been modified and needs to be returned to the phone
remove the phone then reconnect and using 'adb shell'
su
chmod 777 /sdcard/filename.img
dd if=/sdcard/filename.img of=/dev/block/mmcblk0p3
reboot
now after the reboot connect your phone to the wifi and it will be using your new address
Original question below:
got 2 of these Atrix phones.
i have rooted both following this guide
wiki.cyanogenmod.com/wiki/Motorola_Atrix_4G:_Full_Update_Guide
now my one has this installed:
cm-7-20121014-NIGHTLY-olympus.zip
the wifes is still stock.
now we both have been experiencing wifi problems, which i have traced to both phones having the same wifi mac code
98:4B:4A:5D:8D:4C. Resulting in the router not being able to distinguish between them, a right mess.
i have tried following this guide to change my mac address
pocketnow.com/tweaks-hacks/motorola-atrix-4g-how-to-change-wi-fi-and-bt-mac
but changing the address in this file has no effect, its as though the mac address above is a spoof. Not the address stored in /pds/wifi/wlan_mac.bin
i have also tried from terminal 'busybox ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx'
this also does not change my address.
others mention to change the contents of nvram.txt here:
/etc/wl/nvram.txt
this also has made no change
the 2 file locations mentioned contain different mac addresses from the one above.
which file contains this code '98:4B:4A:5D:8D:4C' ?
How do i change the mac address?
i think mac address related to hardware so you can't change it. I have flashed several roms but the mac address is constant, the only change is device name.
Sent from my MB860 using xda app-developers app
lambcutlet said:
which file contains this code '98:4B:4A:5D:8D:4C' ?
How do i change the mac address?
Click to expand...
Click to collapse
/pds/wifi/wlan_mac.bin looks like the right place. But be aware that messing up your PDS could mean quite bad consequences for your phone.
I'd probably dump the entire PDS partition into a file and back it up somewhere if I were you.
voncount said:
i think mac address related to hardware so you can't change it. I have flashed several roms but the mac address is constant, the only change is device name.
Click to expand...
Click to collapse
Nope, wrong.
It's true a MAC is a hardware address, but it's not true it cannot be changed.
ravilov said:
/pds/wifi/wlan_mac.bin looks like the right place. But be aware that messing up your PDS could mean quite bad consequences for your phone.
I'd probably dump the entire PDS partition into a file and back it up somewhere if I were you.
Nope, wrong.
It's true a MAC is a hardware address, but it's not true it cannot be changed.
Click to expand...
Click to collapse
pds backup was performed. My address is different in the 'wlan_mac.bin' file, probably the original F8:7B:7A:xx:xx:xx. i did manage to change its contents but still it appears to be over-ridden by '98:4B:4A:5D:8D:4C'
its weird that both phones have the same mac address
also noticed the bluetooth address is different 00:11:22:33:44:55
there is a program somewhere on my phone over riding the original addresses.
does anyone know what it could be?
has anyone else used the same guide as me to root the phone and ended up with the same mac and bt addresses?
I have 2 Nook tablets. 16 gm. One of them was bricked and I lost the rom partition in the unbrick process, So I can run custom roms but can't register with BN stock. I then copied my rom from the "good" tablet to the "bad" tablet and am able to register both under the same serial #. I should just leave it alone but this bothers me. So all I need to do is edit the one tablets serial number to be correct. Is there a clear way to do it ? So****es post earlier is confusing to me Thanks
Install a root capable file manager go find the file that holds your serial number ->edit->reboot->profit
/devconf/DeviceID
I'm looking for some help verifying a few bits of information before I take a leap and risk bricking my phone. I need to change my bluetooth address. With any luck back to my original hardware address. I do have the original address, as "btnvtool -p" outputs a different address than is reported in 'about phone' -> 'status'. I problem is that both my wife and I have the same phone with the same ROM history, and now we both have the same improper mac address.
By way of links provided by another helpful users I have partial information in Russian. http://4pda.ru/forum/index.php?showtopic=420801&st=6840#entry28414922 post 6853. I think I understand what to do via google translate and my partial understanding of how this works. The post points me to the /misc partition but I can't find any useful information about the partition for this phone that would backup the claims. Also the specific location that the post references, offset 4000, contains a string "ANDROID-BOOT!". While "ANDROI" is hex of 414E44524F49 which matches my incorrect mac address, the fact that it says "BOOT" makes me worry about changing it.
I'm hoping someone can help me any verify that this string isn't part of the boot process, or that the /misc partition isn't required to boot recovery. I feel fairly confident that I could create a flashable zip to restore a backup of this partition if needed. Below is my cleaned translation of the Russian post. If anyone with an e970 and a proper BT address could complete the first half, dd the partition to a file and check out the contents in a hex editor, I would feel much better about doing the rest.
Code:
Hello, using this method you can restore your original Bluetooth addresses. The active mac address is in raw MISC partition at hex offset 4000, it is not spelled out or anything.
perform the following (root is required)
ADB shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.img
and get at the file on the SD card and in a HEX editor zero the MAC address starting at hex offset 4000, save the file. Save the changed file to your phone:
su
dd if=/sdcard/misc.img of=/dev/block/platform/msm_sdcc.1/by-name/misc
reboot
After rebooting the details in the “About Phone” should show the real MAC BT.
----------
So I found a little corroborating evidence to this post. I found this post about the LS970(Sprint LGOG) stating that "All rooted LGOG Bluetooth MAC addresses are 41:4E:44:52:4F:49". Reading the thread a bit, I found a link to a "BT MAC FIX" script found with this kernel.
Looking at what the file does, it uses btnvtool to get the real mac and writes it to byte 16384 ( hex 4000 ) of the misc partition. Seeing as this file has people confirming it works, I took the leap. It worked. Problem solved.
Sound like to me this is a problem as old as unlocking with freegee. Could be wrong but that seems like the common denominator to me from the posts I was reading. And yes for the record, now the dump of the misc partition now reads "******D-BOOT!" *s to hide my real mac.
***Warning, 2015-01-12, This Fix as is doesn't work and causes problems with CM12 on the E970. Will post in thread with details.
I have the exact same issue with mine and my wife's phone. I tried this, and it seems like it should work, but after I reboot my phone, the contents of misc revert to the original (ANDROID...). Any thoughts?
mindstormsguy said:
I have the exact same issue with mine and my wife's phone. I tried this, and it seems like it should work, but after I reboot my phone, the contents of misc revert to the original (ANDROID...). Any thoughts?
Click to expand...
Click to collapse
I believe everyone that used freegee to root/unlock have the corrupted BTmac address. I also believe that it is only an issue when two of these devices try to use BT in close proximity, but you never know what device the person beside you will have.
I had not done anything about my BT until just now. The .zip just puts a script in the userinit.d folder. The script is run every boot. I do not recall what my BTmac address was, but the script does change it from the default.
I deleted the script and rebooted. My BTmac address reverted back to the default. I restored the script and my BTmac address changed back. This shows that the change is not permanent, and the script needs to be run every boot.
Did you flash the .zip, or just extract and run the script?
I've recently upgraded my E970 to CM12 nightly. Just like previous roms the BT Mac address is corrupted and results in my pairing being invalid. My mac address currently reports in "About Phone" as 00:00:00:00:5A:AD. Clearly this is incorrect.
When I tried to install this fix. The init.d script was placed properly, but did not repair the mac address as it did previously. This might be a one off case, but after the script was installed, my phone started acting funny, over heated, and completely drained the battery. The charger I regularly use, an iPad 2.1 amp failed to charge the phone. All it would do was turn on the red notification light solid. I was still able to use the computer usb ports to enter download mode, and start entering the off-charge mode. This port didn't give enough power to fully enter the off-charging mode. The phone made it to the first icon and then shut off, no progress was made.
I needed to switch to a lower output charger before I could gain charge to 5% and boot. As the OS booted it reported 0% charge. I was able to enter airplane mode and reboot. After the reboot the phone functioned well enough to use Solid Explorer to delete the script file from /data/local/userinit.d . After deleting the file my phone was back to functional with the bad mac address.
As I find info I will post it here.
2015-01-13 Update -----
Running the steps of the script file manually, results in a error "dd: stdout: Illegal seek" . Trying to read (if) instead of write (of), I get the same Illegal seek. Might this be part of a new protection with lollipop? I tried editing a dump of the partition as I suggested originally and writing the whole 16mb back. This completes without error, but when I read the partition again the modification was not saved.
Either way my BT Mac address with CM12 doesn't match the expected 41:4E:44:52:4F:49 to match the ANDROID from the file dump, so where is the OS picking up the new address?
Still works for CM11
I noticed my phone and my wifes also had the same bluetooth address. This was messing up my car link. I ran the script and now it shows that I have a different address. I will keep an eye out and make sure nothing else gets messed up. Thanks. I was looking for a fix for some time....