Database Users

Help!! messed up updating cyanogenmod! Bricked??

I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.

Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492

Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??

What!
can you get in the recovery?

Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.

Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!

Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?

Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow

Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?

icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map

OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!

icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window

[Q] couldn't format sd card, accidentally deleted OS, can't mount to computer

Hi I broke my nexus 7 3g. I wanted to reinstall paranoid android and make everything fresh. Checking wipe data with goo manager didn't completely make everything stock so I figured maybe PA saved something to the "sd card", so I tried to wipe external data in twrp and I got unable to wipe /usb-otg, then I figured maybe if I wiped all the other options that might fix it and that just got rid of the OS completely.
I get unable to mount /usb-otg when trying to mount it to my desktop to copy a copy of the rom over because it seems my sd card did manage to get formatted. Unless I'm not choosing the right thing I don't know somebody help please before I throw this thing in the garbage.
I can't get it to show up in the nexus 7 toolkit but I have the donate version of that if by some chance that'll make the process easier. God damn please help me.

I've installed I think every program ever made for windows (gonna have to reformat windows again weeeeeeeee) trying to fix this and they all seem to want my nexus in adb mode but I don't think there's an adb mode when there's no OS installed. I'm willing to pay if that'll get me some help faster.

"mount /usb-otg" is for putting a usb storage device (flash memory key or USB Hard Drive) on a OTG cable attached to the N7 when booted into TWRP recovery.
It is NOT for making the N7 look like a USB mass storage device to an attached PC.
So put your ROM file on a USB key drive (VFAT formatted, not NTFS formatted), and flash it from TWRP "external storage". You don't need ADB to be working if you do that.
If you don't have a big enough flash key or a USB Hard Drive to do this with, then you have two remaining options:
1) Get adb working
2) Get fastboot working (and fastboot flash a stock ROM, and then proceed from there)
good luck

bftb0 said:
"mount /usb-otg" is for putting a usb storage device (flash memory key or USB Hard Drive) on a OTG cable attached to the N7 when booted into TWRP recovery.
It is NOT for making the N7 look like a USB mass storage device to an attached PC.
So put your ROM file on a USB key drive (VFAT formatted, not NTFS formatted), and flash it from TWRP "external storage". You don't need ADB to be working if you do that.
If you don't have a big enough flash key or a USB Hard Drive to do this with, then you have two remaining options:
1) Get adb working
2) Get fastboot working (and fastboot flash a stock ROM, and then proceed from there)
good luck
Click to expand...
Click to collapse
Holy crap I kinda thought the otg thing was because I flashed the kernel for using a charging otg cable. You know what I googled everything under the sun except the error itself. I was serious about the money if you want like $5 or $10 let me know if you got a donate link.
I'm pretty curious to know how to get adb working without an os installed. I'm pretty curious again about using fastboot because I have fastboot and it wouldn't show up on the nexus 7 toolkit etc etc etc. If you don't want to explain them that's fine because I'm pretty sure I'm not gonna mess up this bad ever again and I'm gonna buy a second usb flash drive now that I know I might finally have a reason to have even a single one haha.
Thank you thank you thank you thank you thank you thank you thank you thank you I guess I can throw out my tape and floppy drives now that it's 2013 and we're in the future.

The custom recoveries also run ADB... so you don't need an OS installed to use adb - just a custom recovery.
But there is a catch: ADB from the custom recoveries (either CWM or TWRP) show up on a different USB IDs than what the N7 (Android) OS uses
This little tiny detail effs up just about every newb Windoze user because they get an ADB driver installed for one or the other (either the OS flavor - using Google or Asus drivers, or the custom recovery flavor - using the "Universal Naked Driver")... and then they can't understand "why ADB doesn't work" in the other mode.
Sorry but I'm not going to rehash a tutorial on Windows drivers. I put up a gory long winded story somewhere, wait here it is. Feel free to ignore it. Woe to you if you are using Windows 8.
Rather than profuse "thank you"s, click on the Thanks button. At the end of the year I'm going to trade them in for some brownie points.

Well I clicked the thanks buttons but I just have to type it once more thanks there it is, I'll read that link soon too and I'll click the thanks button on that see ya in the future

[HELP] Retrieving files from broken phone

Soo after spending hours doing a lot of research i seem to be stuck trying to retrieve some files and data from my nexus 6p (my screen is broken and unresponsive soo i cannot click usb mass storage or fully unlock or i guess decrypt) . My bootloader is unlocked and I am running twrp recovery menu. Its rooted with supersu and I am currently trying to mount my internal storage or sdcard (same thing) using adb and adb shell. From my understanding my internal data should be in /sdcard, data, or in the partition /dev/block/mmcblk0 . I am never able to mount it since it seems to be busy. adb seems to be running in root and the shell seems to be running in root as well but i can't seem to access my internal storage. Any more help or advice would be greatly appreciated. I also apologize in advance if this isn't the right place for this post .

Do your buttons still work? Can you boot into recovery, and mount that way?

My buttons still works. Im able to boot into fastboot mode and im pretty sure recovery as well if im able to connect to my device with adb.
edit: Im pretty sure im getting stuck somehow by the default encryption of the nexus 6p and i can't think of a way that i will be able to decrypt . i don't even think i will be able to enable ums.

This may not be what you're looking for but you could try using dd if available and pull the system, data, and sdcard partitions off of your device.
Then you could theoretically flash those onto another 6p, decrypt, and retrieve you files.
I have to say be careful when using dd because its a powerful tool that can easily brick you device.
Thinking about it a bit more made me realize you need a otg cable and some sort of USB drive for that to work. And I'm not sure if twrp auto mounts USB otg drives
Sent from my Nexus 6P using Tapatalk

superchilpil said:
This may not be what you're looking for but you could try using dd if available and pull the system, data, and sdcard partitions off of your device.
Then you could theoretically flash those onto another 6p, decrypt, and retrieve you files.
I have to say be careful when using dd because its a powerful tool that can easily brick you device.
Thinking about it a bit more made me realize you need a otg cable and some sort of USB drive for that to work. And I'm not sure if twrp auto mounts USB otg drives
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Soo far every attempt at getting Ums to pop up or to gain access to any form of data trough usb (otg cable) have seem to fail and trying to use the adb pull command ends with the error (0 files pulled and 0 files skipped) which i would assume is because I don't have the right permissions for those directories which is odd since im rooted and I am running everything in root has well. Since i can't see the screen i can only assume that i am in some form of recovery mode and not just the twrp one if i am able to connect to it trough adb but not UMS( pops up on my windows pc has mtp).

If you're booted into recovery and twrp successfully decrypted it then you should have no issues.
Try to get to the bootloader and flash the latest twrp then boot back into twrp and see if it let's you.
Sent from my Nexus 6P using Tapatalk

superchilpil said:
If you're booted into recovery and twrp successfully decrypted it then you should have no issues.
Try to get to the bootloader and flash the latest twrp then boot back into twrp and see if it let's you.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I have the latest twrp recovery (3.0.2-0) and im able to adb pull the default.prop but I still can't seem to mount any of the internal storage directories. I retrieve the error failed invalid argument when trying to run the adb shell command "mount /dev/block/mmcblk0p44 /emmc" btw emmc is a random dir i made. Same think happens when I try to mount /sdcard or /data/media. Right now I'm trying to Use DD if of has you suggested but the data partition would be to big to create on my device so i would need a way to write it directly to my windows system . I've been trying to follow this guide https://www.packtpub.com/books/content/extracting-data-physically-dd

Once you boot into recovery, doesn't the phone show up on you computer as a drive? Just grab the files that way.

spotmark said:
Once you boot into recovery, doesn't the phone show up on you computer as a drive? Just grab the files that way.
Click to expand...
Click to collapse
No It does not show as a drive. I remember having to swiping my passcode on my device in twrp recovery or even on any initial boots in order to decrypt my drive. I am assuming this is the reason why I cannot see the contents of these directories trough the adb shell. I can see see and adb pull from system and most other directories.
You know what I think my internal drive got wiped somehow and that is why nothing is popping up it is the only explanation i can come up with. I give up.
Edit: So I just got my replacement unit , same make and model nexus 6p with the same set up, rooted ,twrp, and encryption. And it turns out If you do not decrypt your disk, you will not be able to mount or access any data on the internal sdcard. So now my question is, is there a method where Ill be able to send a command or modify a file to decrypt the data on the fly since my screen doesnt work nor respond to be able to mount the disk ?

Is it possible to send commands or modify the command "cryptfs checkpw" to "vold" true adb or would i need to write some app or script? Cause i would be able to do any of the above if the action is actually feasible. Also i apologize if double posting is not allowed.
edit: source of information on encryption can be found here https://source.android.com/security/encryption/

Plug it into a tv to see the screen, and try to use a wired mouse to toggle what you need. It may take some tinkering
Sent from my Nexus 6P using Tapatalk

kyuubie said:
No It does not show as a drive. I remember having to swiping my passcode on my device in twrp recovery or even on any initial boots in order to decrypt my drive. I am assuming this is the reason why I cannot see the contents of these directories trough the adb shell. I can see see and adb pull from system and most other directories.
You know what I think my internal drive got wiped somehow and that is why nothing is popping up it is the only explanation i can come up with. I give up.
Edit: So I just got my replacement unit , same make and model nexus 6p with the same set up, rooted ,twrp, and encryption. And it turns out If you do not decrypt your disk, you will not be able to mount or access any data on the internal sdcard. So now my question is, is there a method where Ill be able to send a command or modify a file to decrypt the data on the fly since my screen doesnt work nor respond to be able to mount the disk ?
Click to expand...
Click to collapse
There's a method of removing pins/patterns/passcode from the device, but I do not know if this would allow TWRP to decrypt the internal storage partition automatically. If I remember correctly from my last nandroid restore where I didn't remove the security, after using this method, when Android boots it goes directly to the unlocked homescreen. Whether or not this is decrypted, or whether ADB can access it, is another matter entirely.
Use at your own risk. I'm not responsible for you breaking your stuff. http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/

tcollum said:
Plug it into a tv to see the screen, and try to use a wired mouse to toggle what you need. It may take some tinkering
Click to expand...
Click to collapse
Probably you already know that it's not possible to connect 6p to TV with HDMI cable (I've tested this myself in the past).
My 6p dropped on the ground smashing screen and then spent few weeks in the drawer. Now I'm trying to recover files from internal memory using external wired keyboard via OTG to type in password (I've set fingerprint protection on, which always requires password after each reboot), but when I connect my phone to PC then it doesn't show any content on it (Nexus 6p appears in Windows Explorer, but doesn't show any files). It looks like my Nexus is still locked. I can't really remember now if password prompt appears straight after rebooting (so I could simply connect keyboard, type in password and press ENTER) or it requires to press something first (slide the screen or so)? Can someone please check and describe full sequence, best with connected external keyboard?

Note 4 locked without USB debugging enabied (fngerprnt / bckup pword not recognised)

Hi
I have a Galaxy Note 4 (SM-N910G) and don’t normally muck around with the system. I have limited experience with Android.
My phone is locked (with important data stored in it)– a couple of days ago (presumably after a system upgrade) it suddenly would not recognise my fingerprint nor backup password.
I tried unlocking the phone using Android Device Manager but although I could get my phone to ring or display text, I could not change the password after locking the phone.
I called Google who said that Android Device Manager only works on earlier Android Versions - ?4 and below and most likely my phone would be running Marshmellow.
I called Samsung who said my only option is to restore to factory settings.
I wanted to use ADB
(to enter: adb shell
cd data/system
su
rm *.key) and downloaded it and tried to use it from the c:\ prompt but I don’t have USB debugging enabled. No device was recognised when running ADB.
I had not registered for a Samsung account so I could not use Find My Mobile.
I tried to apply an update via external storage in recovery mode (I downloaded files such as Lockscreen_Security_bypassV1.1.zip or Pattern-Password-disable.zip) but unfortunately when I tried to apply them, it came up with E:footer is wrong, E: signature verification is required.
(I also tried “Android Multi Tools”).
I do not have CMN recovery loaded nor Aroma+File+Manager
My question is: should I try and use Odin (have downloaded odin3_v3.11.2.zip) and TWRP to try and enable USB debugging or try to disable footer/signature verification??
Any other suggestions to try and unlock my phone???
At the minimum this has been an education!
Thank you for your help!

Recover rooted NST with broken LCD?

Just checking it there is some way to recover files. I previously rooted it and can't remember if that means there's any way to get at it via ADB or otherwise to recover files before transfering to a new device

Well, if you have ADB working you can just transfer the files.
Or you could use my AdbSync.exe (along with ADB) to backup.
Code:
C:\>mkdir whatever
C:\>adb devices
C:\>adbsync /hcsu /s /v C:\whatever sdcard

ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction

mrbryan said:
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
Click to expand...
Click to collapse
You're the second person in a week or so that seems to have this issue and it got me curious. There's a message at the beginning of NookManager about starting WiFi if you want to directly connect with the device via SSH(?) or ADB. I've always ignored it but I just tried it to see what would happen. After you elect to start WiFi (your NST must have been known to your network beforehand, password entered, etc.), you are given the option to start either SSH or ADB (the IP address is displayed at the top of the screen).
When I chose ADB I was then able to start up ADB on my PC and connect to the IP address shown on the NST screen. Of course.....if your screen is broken........Maybe you know the IP address of your NST already or could find it by starting WiFi and then consulting your router?
Anyway, the advantage with NookManager is that everything is done with the side hardware buttons. If you can't read your screen at all I can see that even that would be a problem, though. If you have some partial display, you might be able to limp along until you have ADB connected and then handle everything from your PC. Or I could supply you with a button-push sequence to try.
To just get this working you can make a NookManager card--no need to make the updates I described elsewhere.

thanks so much for the suggestion. I'll have to think that through and whether I have my current wifi set up ( edit: in the nook already).
maybe I can hack around in the scripts for nook manager in case I can set it to go right to the ADB on boot and inject a wifi name & key too

Get an image for the old noogie and put it on an SD card.
Boot up, you should have ADB.
Or do the whole OmapLink procedure and boot from there.
Or connect to the 1.8V UART root console inside the case.