I'm going to try mine again with the newer image and if that doesn't help, go back and exchange it for a Kingston. Most of my cards here are Sandsisk and Kingston -- the Class 4 is a Kingston. My newer one is Patriot, which is a brand I've not had any problems with when it comes to notebook memory and they were the only brand in stock that had a 16GB option.
[How-to][NEW VERSION] Run Nookie Froyo off SD card
- Thread starter Will Shanklin
- Start date
I'm going to try mine again with the newer image and if that doesn't help, go back and exchange it for a Kingston. Most of my cards here are Sandsisk and Kingston -- the Class 4 is a Kingston. My newer one is Patriot, which is a brand I've not had any problems with when it comes to notebook memory and they were the only brand in stock that had a 16GB option.
I think I remember reading about other people having problems running nookie on Patriot cards.
I put 59 img on and so far no problems.
With the 58 img I had problems a few minutes in and then after shutting down the NC it would no longer boot. I've shut this down and restarted with 59 and all is good.Anyways, I'll see how it goes and if it starts to bug out again, I'll exchange it.
Hey,
I install on the SD card and it runs just fine but now I try to install the google apps and the ADB commend returns "device not found"... what did I do wrong???
I install on the SD card and it runs just fine but now I try to install the google apps and the ADB commend returns "device not found"... what did I do wrong???
Read page 2. Will posted a longer method if you are having problems with the driver:
NookColor USB ADB - nookDevs
Let me know if you get past this. I'm having problems myself.
I'm thinking you downloaded the unmodified 0.5.9 image. The image in this OP has the SD card fix already in place.
If you want to fix it from where you are now without restoring, do this (credit deitiphobia):
Download this file: vold
Use either Root Explorer or adb to place it in system/bin (replacing the old vold) BUT CHANGE THE PERMISSIONS:
In Root Explorer, just long press on any other file in system/bin and change the new vold to match
In adb: enter the following (with vold in your adb tools directory):
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push vold system/bin/vold
adb shell
cd /system/bin
chmod 6755 vold
ls -l vold
Then reboot, and the error will be gone
Last edited:
Ok so I did everything corectly, I got froyo working and finaly got device not found to go away. adb seems to work corectly, I push the system files and I get no errors, i reboot expecting to see google apps but nothing. here is what I get in adb
I tried rebooting before trying this many times, i think all my drivers are installed, what am I doing wrong?
Code:
C:\Users\Name>cd C:\Program Files (x86)\Android\android-sdk-windows\platform-
tools
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell moun
t -o remount,rw /dev/block/mmcblk1p2 /system
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb push C:\Pr
ogram Files (x86)\Android\android-sdk-windows\tools\system /system
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
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 r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - 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.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb reboot
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>I tried rebooting before trying this many times, i think all my drivers are installed, what am I doing wrong?
Hi all, first thanks! I had no problem getting nookie up and running on a 4g class 4 card adb working but here is the thing when I use adb at the comman line the cursor moves to the next line and blinks how long should this take before command prompt returns? read through the posts but no sign of my problem.
Make sure your screen stays on when using adb with nookie. It'll do that if the display times out.
Yeah, none of that will ever affect Nookie. You could have a Nook that, by all appearances, seems to be bricked, and chances are, it'd still run Nookie from the SD.
Hi, can you help a noob out ? How do you turn on SuperUser when you restart Android ? My macbook pro is giving me error:device not found and nothing listed under adb devices.
Thanks
Super User starts automatically, but if you've never used it before, it couldn't hurt to manually open the app - the app called SuperUser. I've never heard of that as being necessary for adb, but if he said it worked for him, can't hurt giving it a shot.
I've tried that twice and still cant get my MacBook Pro to list my device. My NC does however indicate USB debugging connected and USB connected at the top pull down menu bar, just nothing listed on adb devices. It is an earlier MacBook Pro, 1.83 core duo, and I've had issues with some external hard drives and not enough power.
Thanks.
Thanks.
ugh. i constantly get this.
c:\android-sdk-windows\platform-tools>adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
error: device not found
when doing "ADB Installation of Google Apps" step...its in Manage -> Devices and Froyo is booted up on the NC, but to no avail, this cursed 'device not found' is killing my success.
****** Edit...ok i saw post 106...let me try that attempt and see. very cool.
c:\android-sdk-windows\platform-tools>adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
error: device not found
when doing "ADB Installation of Google Apps" step...its in Manage -> Devices and Froyo is booted up on the NC, but to no avail, this cursed 'device not found' is killing my success.
****** Edit...ok i saw post 106...let me try that attempt and see. very cool.
Last edited:
I'd like to see ADB wireless preloaded. Then you can forget about these ADB connection problems via USB.
Technically, I--or anyone with win32diskimager or adb--could upload an image with Google Apps, adb wireless, and Angry Birds thrown in, but then you get on legally questionable ground because you're distributing non-open source content (free doesn't always equal open source). Cyanogen ROM's used to include Google apps, but they got a cease/desist from Google, so now it's a separate "optional" download. Most devs and ROM distributors have followed similar suit, and, non-conformist though I am, I don't want to make the wrong kinds of headlines for Android Central. It's pretty easy to install Google apps, and getting familiar with basic adb setup and commands could come in handy for doing other cool things down the road.
Similar threads
- Question
Trending Posts
-
-
Samsung Pay doesn't work with my non samsung phone on Galaxy Watch 8 Classic
- Started by Joltpost
- Replies: 0
-
-
-
Facebook
Twitter
Instagram