This was purely experimental for me, but it worked. Iron Man 3 Texture Pack 1.5 2 Download. 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. Two MicroSD card required. If you're using Windows you need some program that can perform disk dumps.
How to change Android ID,SSN & Device ID on Android. Device ID, Sim Serial Number. In this article We will be covering the method to change Android ID.
I use Ubuntu. I don't know if the commands are similar in windows, sorry. 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: $ dd if=/path/to/file/mmcblk0p5.img of=/dev/mmcblk0Wait 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.
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 # ~ exitIn 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.
Code: Android Debug Bridge version 1.0.25 -d - directs command to the only connected USB device returns an error if more than one USB device is present. -e - directs command to the only running emulator.
Returns an error if more than one emulator is running. -s - directs command to the USB device or emulator with the given serial number. Overrides ANDROID_SERIAL envivornment variable. -p - simple product name like 'sooner', or a relative/absolute path to a product out directory like 'out/target/product/sooner'. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be an absolute path. /dev /proc /sys /systemI did it both as an admin and a super user on the mac and I got about the same results.
My Droid was in the regular boot mode. I have not tried booting into the restore or safe modes and tried a 'pull'. One last thing. I noticed the 'adb root' command too, but I get an error back saying that you can not root on a production build of android. Perhaps there is a way to fool adb into thinking you have a developer device/build, maybe by altering the 'build.properties' file. I haven't looked into that, nor do I really know if it would work.
I'm really not an android developer, but if anyone out there is, maybe they could tell us what lets the adb shell know that a device is a production build, rather than a development build. I better get going now. Have fun hacking your Droid!!:icon_ banana. Code: Android Debug Bridge version 1.0.25 -d - directs command to the only connected USB device returns an error if more than one USB device is present. -e - directs command to the only running emulator. Crack C-map Charts. Returns an error if more than one emulator is running. -s - directs command to the USB device or emulator with the given serial number.
Overrides ANDROID_SERIAL envivornment variable. -p - simple product name like 'sooner', or a relative/absolute path to a product out directory like 'out/target/product/sooner'. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be an absolute path.
/dev /proc /sys /systemI did it both as an admin and a super user on the mac and I got about the same results. My Droid was in the regular boot mode. I have not tried booting into the restore or safe modes and tried a 'pull'. One last thing. I noticed the 'adb root' command too, but I get an error back saying that you can not root on a production build of android.
Perhaps there is a way to fool adb into thinking you have a developer device/build, maybe by altering the 'build.properties' file. I haven't looked into that, nor do I really know if it would work. I'm really not an android developer, but if anyone out there is, maybe they could tell us what lets the adb shell know that a device is a production build, rather than a development build. I better get going now. Have fun hacking your Droid!!:icon_ banana. Well here's my current situation. If it helps you to know, my adb directory is C: Android android-sdk-windows tools adb.
Here's what i put into the msdos window (black is what was there, red is what i typed): C: Documents and Settings Owner>cd C: >Android android-sdk-windows tools adb Android Debug Bridge version 1.0.25 (plus crapload of adb stuff here) C: >Android android-sdk-windows tools adb shell $ adb -s [my serial number] shell adb -s [my serial number] shell adb: permission denied $ so how do i get permission allowed? I tried it a couple times, change things up, added or removed the [ ] on either end of the serial number, tried the super user (su) command. Well here's my current situation. If it helps you to know, my adb directory is C: Android android-sdk-windows tools adb. Here's what i put into the msdos window (black is what was there, red is what i typed): C: Documents and Settings Owner>cd C: >Android android-sdk-windows tools adb Android Debug Bridge version 1.0.25 (plus crapload of adb stuff here) C: >Android android-sdk-windows tools adb shell $ adb -s [my serial number] shell adb -s [my serial number] shell adb: permission denied $ so how do i get permission allowed? I tried it a couple times, change things up, added or removed the [ ] on either end of the serial number, tried the super user (su) command. Click to expand.Here is what works for me.
Make sure that you have usb debugging enabled in your settings on the phone, and my phone is unmounted. I have changed my directory structure to match yours. At the c:, type cd Android android-sdk-windows tools this should give you c: android android-sdk-windows tools>at this point I just type: adb shell (no switches) This is what I see after: adb shell * daemon not running. Starting it now* * daemon started successfully * $ then I type: su this should give you the # Then you should be in. Not sure if you need to physically be in the tools subdirectory when invoking the shell, or it is the switch, or perhaps the debugging switch on the phone, but the above always works for me.
Sorry man, I'm trying. You don't have to apologize, you been a fantastic help actually! I'm alot farther than when i started, thanks to you.
So i tried this a few times, and the first time i did it, it didn't give me the #, so i tried it again, and now it is displaying it, but that code to see if i can send commands to my phone stopped, and i didn't get anything about the daemon not running then starting up. But the pop up window came up on my phone to confirm superuser access, so i guess that's good. Now to try something to confirm this.