Related
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?
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.
This was purely experimental for me, but it worked. And now I have my serial number back.
Pre-requisites:
1. You need CWM, running internal, or at least two microSD cards to be running from sd card.
2. Two MicroSD card required.
3. If you're using Windows you need some program that can perform disk dumps. I use Ubuntu... so... I don't know if the commands are similar in windows, sorry.
4. You'll need someone else' serial number. In other words, you'll need someone else' backup of the /rom partition. Check lavero.burgos unbrick topic. I think there is one on there.
This should be at least somewhat risk-free. Since it doesn't actually tinker with settings
Okay, so boot into internal cwm on your Nook. Make sure you have an sdcard in your nook. Then run adb:
Code:
$ adb start-server
$ adb devices
Make sure you see your device and it shows it in recovery mode.
Code:
$ adb shell
~ # mount sdcard
~ # dd if=/dev/block/mmcblk0p5 of=/sdcard/blk/mmcblk0p5.img
~ # exit
$ adb pull /sdcard/blk/mmcblk0p5.img /path/to/file/mmcblk0p5.img
$ adb shell
~ # rm /sdcard/blk/mmcblk0p5.img
~ # exit
At this point you insert your sdcard into your computer. Depending on what adapter you use, we need to make sure that you are going to use the correct device... so...
Code:
$ fdisk -l
Other than your Hard Disk's partitions (usually the first four), you should see a second one, either /dev/mmcblk0 or /dev/sdc depending on the adapter, but make sure it is the same size as your SD card, so you know which one you are going to be using. Once you verify which one is yours go ahead and umount it.
Code:
$ dd if=/path/to/file/mmcblk0p5.img of=/dev/mmcblk0
Wait for it to finish, shouldn't take longer than a half-minute, once it's done, Go ahead and mount it again, you should see the only partition as "rom", and two folders: devconf, and log.
Navigate to devconf, and there's a bunch of other files. Open "DeviceID" in vim or notepad or something. This is your Serial No., or where it should be anyway. On your nook, if you pop open the little MicroSD flap, you will see the device' serial number. Delete whats in that file, and type your Serial No. on there. Close and don't forget to save it. Now open "SerialNumber" and delete what's on there, and key in YOUR serial number. Close and save.
Umount your sdcard again. Delete the original mmcblk0p5 (/path/to/file/mmcblk0p5). Then jump into shell
Code:
$ dd if=/dev/mmcblk0 of=/path/to/file/mmcblk0p5
$ adb push /path/to/file/mmcblk0p5 /sdcard/blk
$ adb shell
# ~ dd if=/sdcard/blk/mmcblk0p5 of=/dev/block/mmcblk0p5
# ~ umount /sdcard
# ~ exit
In cwm go into advanced/reboot recovery. Let it reboot. And then when it's in cwm run "adb devices" and verify your serial number is there.
Thanks to Pete1612 and lavero.burgos ! Hopefully Pete1612 will test out this method too. This should be relatively easy, it's not hard. Just time consuming. -_-
Once again, let me know if I made any mistake
I will as soon as I get the I/O error figured out
Sent from a better galaxy
Pete1612 said:
I will as soon as I get the I/O error figured out
Sent from a better galaxy
Click to expand...
Click to collapse
The I/O error means the partition is damaged, however when unmounted the sdcard and re-inserted it, it seemed to work fine, so I went with it.
I took a different SD card and it worked.
Sent from a better galaxy
Probably keep this but it's u service the as card tab I. the back of the Cover
@ae1990
1. Type reply
2. Verify that what you typed was correct
3. Submit
I think you forgot step 2.
Edit-
That came off ruder than intended, I would actually like to know what you were trying to say.
Sent from my SCH-I500 using Tapatalk 2
I think have a way:
1. Copy mmcblk0p5 from nook tablet fine and push to sdcard
2. Use dd command
dd if=/sdcard/blk/mmcblk0p5 of=/dev/block/mmcblk0p5
3. In Cm7 ( boot sdcard) or stock rom have root, i use root exploer change serial in file devices id, serialnumber in rom/devconf.
I had changed my nook by this way. It success, it pass b&n :0
a much easier method... from any rooted nook with ADBD enabled.
Get either adb shell or a terminal and change to root user by issuing the "su" command.
copypasta this block
Code:
mkdir /data/local/mnt
mount /dev/block/mmcblk0p4 /data/local/mnt
Serial=`cat /data/local/mnt/devconf/SerialNumber`
echo "Your Nook Tablet Serial Number is: $Serial"
You will receive a message that says "Your Nook Tablet Serial Number is: ************"
OP is convoluted.
AdamOutler said:
a much easier method... from any rooted nook with ADBD enabled.
Get either adb shell or a terminal and change to root user by issuing the "su" command.
copypasta this block
Code:
mkdir /data/local/mnt
mount /dev/block/mmcblk0p4 /data/local/mnt
Serial=`cat /data/local/mnt/devconf/SerialNumber`
echo "Your Nook Tablet Serial Number is: $Serial"
You will receive a message that says "Your Nook Tablet Serial Number is: ************"
OP is convoluted.
Click to expand...
Click to collapse
OP has made a guide to restore it.
Yours is a way to print it out *if* its there, anyone can read it under the sd card latch so i dont see your reasoning of this post.
Hello, Can you help a noob with this ? I am at a command prompt. Wrong serial # Recovery
now what exactly ? Thanks
Hey I'm not sure if this is right, but can't you just lift up the tab where the sd card goes? It says SN: followed by a bunch of numbers.
When I needed a new charging cable, they asked for the serial number, and I just read it from there.
Sorry if this isn't what you guys are talking about, just thought I'd post.
ACL3 said:
Hey I'm not sure if this is right, but can't you just lift up the tab where the sd card goes? It says SN: followed by a bunch of numbers.
When I needed a new charging cable, they asked for the serial number, and I just read it from there.
Sorry if this isn't what you guys are talking about, just thought I'd post.
Click to expand...
Click to collapse
Thanks
the thread is to recover a sn that is MIA or incorrect for the nook in use. Some have lost their sn (no longer in nt) or replace an incorrect sn with the correct sn.
What if you can't see your NOOK TABLET?
My problem here is I can't get my computer to see the NT. When I update the drivers, it brings it up as an android phone and under that says "Android Composite ADB Interface". Any help. I think I might have completely screwed this up.
I realize this thread is old but I've been trying to go through the process. My first question is how large does the mmcblk0p5 get when you dd it? I was using a 2gb SD and the file took up 2gb then. My second question is if anyone knows how to complete the final push back to the SD card in the nook. It begins to push but after some time the nook screen flashes and it seems to hang. Thanks in advance.
Just use es explorer with root privileges heh.
So would I just copy the file to the sdcard, then once that's done transfer the card back to the nook, and use the es explorer? I'm not quite sure how to do exactly what you stated.
Boot rom , open es give root rights go to / rom find file edit it onthefly, save reboot done
Demetris said:
Boot rom , open es give root rights go to / rom find file edit it onthefly, save reboot done
Click to expand...
Click to collapse
Really, it's that simple? Wow, and I was working through all this last night!
I just rooted my Prime using the new method. It has an unknown serial. I found this ratchet tool: http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
How can I get it to work? When I type adb push ratchet /data/local/, I get an error saying "failed to copy 'ratchet' to '\data\local\\ratchet' : Permission denied.
have to type in "su" to get root rights
I have uploaded a screenshot of the problem.
I can't type su before I enter adb shell. And when I do, the device is not found. Drivers are installed. It is recognized in my computer.
Okay, so I manually copied the ratchet file to the tablet using a file manager. Then in ADB I typed the commands. It asked for serial number, I entered it. Told me to restart and it should be fixed but the serial number is still unknown in settings
Any ideas on how to get it to work? Or does it just not work on jellybean and I'll have to send it in (again) ?
QUOTE=sahilcc7;40175980]Okay, so I manually copied the ratchet file to the tablet using a file manager. Then in ADB I typed the commands. It asked for serial number, I entered it. Told me to restart and it should be fixed but the serial number is still unknown in settings
Any ideas on how to get it to work? Or does it just not work on jellybean and I'll have to send it in (again) ?[/QUOTE]
You could try asking for help from one of the developers of ratchet tool.
http://forum.xda-developers.com/newreply.php?do=newreply&p=40175980
https://github.com/IEF?tab=activity
I am willing to supply logs and experiment if we can get some help.
Download file for Ratchet
Hello,
Not sure if I'm supposed to be posting on such an old thread (let me know, I'm new). I'm getting the "unknown serial" error on my TF700T. I'm trying to download ratchet using the link that was provided, but all I'm getting is a 404 error, so can't download it. I cannot for the life of me find anywhere else to download that file, they all point to that broken site. Does anybody happen to still have that file that they would be willing to send me? I would appreciate it so much!
Hello,
Following erasure of all data in recovery mode ( wipe date / cache / system) , I finally managed to reinstall a origin ROM .
Unfortunately , I did not know I had deleted all of my data.
I managed to get the IMEI code with SN_Writer_Tool_v1.1632.00 : Working
Unfortunately data remains that I can not change .
my serial number (SN ) is: 0123456789ABCDEF . I do not know from where it comes but it has nothing to do with the original number.
Can you give me the manipulation that allows me to restore this No. ??
I also noticed that the SNID / NS were "invalid" on the phone.
NVRAM is not present ?? I do not think I have a bootloader too.
HELP !!!
thank you
jblefou62 said:
Hello,
Following erasure of all data in recovery mode ( wipe date / cache / system) , I finally managed to reinstall a origin ROM .
Unfortunately , I did not know I had deleted all of my data.
I managed to get the IMEI code with SN_Writer_Tool_v1.1632.00 : Working
Unfortunately data remains that I can not change .
my serial number (SN ) is: 0123456789ABCDEF . I do not know from where it comes but it has nothing to do with the original number.
Can you give me the manipulation that allows me to restore this No. ??
I also noticed that the SNID / NS were "invalid" on the phone.
NVRAM is not present ?? I do not think I have a bootloader too.
HELP !!!
thank you
Click to expand...
Click to collapse
Help please. I did find any answer in the forum.
what phone is that?
My mediatek soc phablet came stock with the same serial number.
It is very possible your problem with imea number is unrelated to your serial number. I suggest finding a stock complete rom and start again from fresh.
OLderDan said:
It is very possible your problem with imea number is unrelated to your serial number. I suggest finding a stock complete rom and start again from fresh.
Click to expand...
Click to collapse
Hello,
my phone is a Acer Z410.
I use a recovery rom from acer to format it.
i think the problem is link with the NVRAM because is missing too.
I try to change barecode with MAIU but i don't have file et i don't know where i car download a NVRAM datebase for it....
This works for me on Oukitel K6000 Plus:
https://stackoverflow.com/questions...o-phone-are-connected-on-a-pc-can-i-change-th
echo -n "XXXXXXXXXXXXXXXX" > /sys/class/android_usb/android0/iSerial
Untill reboot, but it's a starting point.
jblefou62 said:
Help please. I did find any answer in the forum.
Click to expand...
Click to collapse
same happen to my celpon . my unit is Blu Grand Max - G110Q
How to change serial number ?
0123456789ABCDEF looks like a emulator or AOSP serial number
Check your default.prop or build.prop serial number
Code:
adb shell getprop | grep serial
[ril.serialnumber]: [0123456789ABCDEF ]
[ro.boot.serialno]: [0123456789ABCDEF ]
[ro.serialno]: [0123456789ABCDEF ]
and change it to yours
Code:
adb shell setprop ro.serialno YOURSERIALNUMBER
Edit build.prop or default.prop for persistent
Yablio said:
0123456789ABCDEF looks like a emulator or AOSP serial number
Check your default.prop or build.prop serial number
and change it to yours
Edit build.prop or default.prop for persistent
Click to expand...
Click to collapse
I already checked it in build.prop but the serial number is not there.
France Mari said:
I already checked it in build.prop but the serial number is not there.
Click to expand...
Click to collapse
not much info about this, sadly. Got this generic serial number issue right now on a Blackview Max 1, MT6763
Yablio said:
adb shell setprop ro.serialno YOURSERIALNUMBER
Click to expand...
Click to collapse
adb shell (even under su) doesn't give permission, is there a way to get permission to write
Code:
ro.boot.serialno
ro.serialno
Global_V12.0.7.0 (redmi note 9)