[Q] Nook Color Root?
- Thread starter Zed Snardbody
- Start date
error not recognized
I promised myself i'd avoid being another annoyance but i can't get through this last bit! my nook is now recognized in device mananger as an android phone. I've updated the driver for the actual nook in the devices and priters section. i go through each command promt step and BAM "error device not found"
i've killed adb server, unplugged the nook and reconnected it all but still nothing. i almost woke my wife up yelling at my monitor! help...
I promised myself i'd avoid being another annoyance but i can't get through this last bit! my nook is now recognized in device mananger as an android phone. I've updated the driver for the actual nook in the devices and priters section. i go through each command promt step and BAM "error device not found"
i've killed adb server, unplugged the nook and reconnected it all but still nothing. i almost woke my wife up yelling at my monitor! help...
Very nice instructions (practically idiot proof)! I wanted to ask if this sideloading means installing APK's and that it or is that something done on a rooted device (meaning this process roots as well)? Thank you!
PS. I believe this should work in Vista?
http://www.kandroid.org/android_pdk/telephony.html
Android's Radio Interface Layer (RIL) provides an abstraction layer between Android telephony services (android.telephony) and radio hardware. The RIL is radio agnostic, and includes support for Global System for Mobile communication (GSM)-based radios.
Not sure it's gonna help us.
Gettin' goin' on Mac OS X...The Hints n' Tips
Ok. The big "oops" points:
1. dd must be used on the whole device, not a partition:
What you need to do here is get a formatted microSD mounted via the Finder via whatever means you have. Use Disk Utility to determine the device path "/dev/disk<a number>s<another number>" which would be spoken as "dev disk one, slice one" (for example).
Next, you will want to click *unmount* in disk utility NOT EJECT, and when you run the dd command in the terminal, you want to do /dev/disk<a number>, e.g dd if=theNooter.img of=/dev/disk<a number>
If you get this part right, the rooting happens correctly, automatically. Per the guide, Mac OS X will tell you it has found new devices.
Once you get to this point, really, you're done. The only thing you need to do after that is paste this into a Terminal window...*but there is a catch* so read past it:
Unless "adb" is in your path, this will not work. The easy solution is to paste the following into a terminal:
<-do NOT hit return or add any spaces.
Then, drag the tools folder from the android SDK to the Terminal window, then hit return. You can now do:
And you are in business.
Let me know if/how that works out for ya.
-K
Ok. The big "oops" points:
1. dd must be used on the whole device, not a partition:
What you need to do here is get a formatted microSD mounted via the Finder via whatever means you have. Use Disk Utility to determine the device path "/dev/disk<a number>s<another number>" which would be spoken as "dev disk one, slice one" (for example).
Next, you will want to click *unmount* in disk utility NOT EJECT, and when you run the dd command in the terminal, you want to do /dev/disk<a number>, e.g dd if=theNooter.img of=/dev/disk<a number>
If you get this part right, the rooting happens correctly, automatically. Per the guide, Mac OS X will tell you it has found new devices.
Once you get to this point, really, you're done. The only thing you need to do after that is paste this into a Terminal window...*but there is a catch* so read past it:
Code:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"Unless "adb" is in your path, this will not work. The easy solution is to paste the following into a terminal:
Code:
export PATH=$PATH:Then, drag the tools folder from the android SDK to the Terminal window, then hit return. You can now do:
Code:
sudo sh -c "mkdir -p ~/.android; echo 0x2080 > ~/.android/adb_usb.ini; adb kill-server; adb devices"And you are in business.
Let me know if/how that works out for ya.
-K
You should see 7 different Functions under the Hardware Tab of the Nook Properties if you did it correctly:
Android Composite ADB Device
B&N Ebook Disk USB Device x2
2 drive letters
USB Composite Device
USB Mass Storage Device
If all of these are not there, then the drivers are not installed correctly. Try uninstalling the drivers, disconnecting the nook and connecting it again.
Awesome...that is truly step by step...I can't wait to try it out.
When I try to "mount //./,f>".....I mean at the very beginning...I get "Device or Resource Busy"
This is similar to when I was trying to use WinImage.
What is holding onto that card that is stopping writing to it?
Anyone?
When I try to "mount //./,f>".....I mean at the very beginning...I get "Device or Resource Busy"
This is similar to when I was trying to use WinImage.
What is holding onto that card that is stopping writing to it?
Anyone?
Yup, it's all there, i've gone the delet and re-install route twice and reset the computer also (just incase) any other suggestions? thanks for the quick reply btw.
Attachments
I'm trying to run this command
mount //./d: /dev/sd3
My SD Card came in as drive d:
Thanks for your help
No, i get that ... which error do you get:
mount: /dev/sd3: device or resource is busy
or
mount: //./d:: device or resource is busy
Side note: try using /dev/sdd instead of /dev/sd3
The first.../dev/sd3....I will try your suggestion
Edit: sdd seemed to work...moving on down the line of instructions
Edit: sdd seemed to work...moving on down the line of instructions
Stupid question...how do I get my memory card back to the original size? I used winimg originally.
Yeah, you can't use numbers there (that's why I had the whole convoluted disk number into zero-indexed alphabet thing in my instructions).
Top Liked Posts
-
There are no posts matching your filters.
-
4
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
ok guys. this is the underside of the board. i took a ton of pictures. i put my NC bac together. still working as it should
hope this little contribution helps. im quite excited for android 2.2 on my nook. this device "feels" very well built, and its really the size i want. now we just need a real andoid experience and ill be one happy nook color owner.
let me know if we need any more photos or close ups, i can borrow a macro lens if wee need photos of something really close up21builing an MLO file ?
I don't agree completly with you. We can experiment few things and develop some POCs like ... The MLO must fit in the 64k sram of the omap3621. We can do a lot a things within 64k like initialise the musb and send the emmc content through it. I'm working to customize my MLO file (from igep 020 card which is a very good one !) after success I will able to compile the same file for NC. Now my NC is somewhere between Los Angeles and Europe I hope to receive it soon ...
Cheers
Occip
