Have searched to see if others have identified this difficulty..............................can't find anything, so here goes. In the past I've dealt with the battery not charging. through trial and error, I seemed to have licked that problem (knock on wood) only to find that I still cannot use my touchpad due to the SORRY TOO MANY CARDS OPEN error message. Nothing is open. looking at the desktop screen with nothing open. I've tried to "go in" different ways, with no luck///
thank you for your suggestions.....ps I know very little about what I'm reading on this forum. speak in "INFANT" if you can. Is there an icon for a baby?
Remember "baby" doesn't understand much, but ............no changes have been made to my "out-of-the-box" hp touchpad. it is a "virgin".
jonellgrier said:
Have searched to see if others have identified this difficulty..............................can't find anything, so here goes. In the past I've dealt with the battery not charging. through trial and error, I seemed to have licked that problem (knock on wood) only to find that I still cannot use my touchpad due to the SORRY TOO MANY CARDS OPEN error message. Nothing is open. looking at the desktop screen with nothing open. I've tried to "go in" different ways, with no luck///
thank you for your suggestions.....ps I know very little about what I'm reading on this forum. speak in "INFANT" if you can. Is there an icon for a baby?
Click to expand...
Click to collapse
On the bottom left you'll find 3 buttons. Back, home and menu. Press the menu button. A whole bunch of previously opened apps should show up. Press each one and 'fling' to either side. When they're all gone you should be able to use your TP. Android should be handling this automatically. You might want to reinstall android.
First of all, make a backup, just in case. Then run acmeuninstaller. In webos run ' remove android'. If you don't have it, download it from preware. If you don't have preware, install it using WOSQI. Then install android, using acmeinstaller3. As long as you're at it, upgrade cwm and moboot. Here's the link to the thread where you can get the files : http://forum.xda-developers.com/showthread.php?t=2080977
I think you have assumed this user is on Android - that is a WebOS error he is reporting.
Googling the error (WebOS too many cards) gives quite a few hints particularly linked to uberKernel. Suggestions are to check what WebOS 'add-ins' are installed.
EDIT - seems like others are reporting this on WebOSNation with it happening for no apparent reason recently - http://forums.webosnation.com/hp-touchpad/310234-touchpad-keeps-telling-me-too-many-cards-open.html
reboot or reset?
chicle_11 said:
On the bottom left you'll find 3 buttons. Back, home and menu. Press the menu button. A whole bunch of previously opened apps should show up. Press each one and 'fling' to either side. When they're all gone you should be able to use your TP. Android should be handling this automatically. You might want to reinstall android.
First of all, make a backup, just in case. Then run acmeuninstaller. In webos run ' remove android'. If you don't have it, download it from preware. If you don't have preware, install it using WOSQI. Then install android, using acmeinstaller3. As long as you're at it, upgrade cwm and moboot. Here's the link to the thread where you can get the files : http://forum.xda-developers.com/showthread.php?t=2080977
Click to expand...
Click to collapse
I'm going to try the reboot, which I'm hoping is holding down power button while simultaneously pressing center of screen until hp logo appears!?
When i'm powered up we'll see if it worked!!!!!!!!! THANKS
Related
something interesting happened to my NC last night. i was messing around with system apks, trying to get better access to the system settings. i copied Settings.apk and SettingsProvider.apk from the 2.1 emulator to /system/app the NC. they didn't work, so i replaced Settings.apk with the original, but forgot to replace SettingsProvider.apk. bonehead mistake. anyway, upon rebooting, the device was stuck in a bootloop. it would get to the white "Nook Color, by Barnes and Noble" boot animation, and just loop over and over. i tried the factory reset twice, but as i expected, it didn't help.
i decided to give up for the night, and left the NC plugged into AC power, bootlooping over and over, just to see if anything would happen. after about 30 minutes, i tried to shut it down by holding the power button. the screen went off, and i set it down. when i looked back a few seconds later, the NC was booting again. this time, it came to the screen shown in the attached photo. on the screen, it says "A new software update is being installed. This will take a few minutes."
the process finished, and the device booted up into a fresh, clean, non-rooted 1.0.0 installation! a real software update wasn't installed. it seems the device decided to reflash the original ROM on itself. can it be that the NC is smart enough to know when something is catastrophically wrong, and flash back to stock? either way, i'm happy to have my NC back in business
pokey and I were talking about this in another thread (though he's better at dissecting this stuff than I am). There's a counter for unsuccessful boot attempts, and after 8 it apparently flashes "factory.zip" from partition 3, which is a full clean factory dump.
This actually happened to me, sort of, two nights ago. I was messing around with system settings, but didn't change anything too important...or so I thought.
Shortly after, I was using my Nook, as it was working normally, and the initial setup screen popped up, said something about being unable to authorize my account, and then went ahead and factory reset itself,forcing me to have to re-root. Pretty annoying, and it was odd, since my Nook seemed to be working fine.
It may be worthwhile to make a modified factory.zip so devices wouldn't lose root, no?
I haven't yet encountered this problem, but it would suck to have to reformat my microSD card if this should happen.
tokyomonster said:
This actually happened to me, sort of, two nights ago. I was messing around with system settings, but didn't change anything too important...or so I thought.
Shortly after, I was using my Nook, as it was working normally, and the initial setup screen popped up, said something about being unable to authorize my account, and then went ahead and factory reset itself,forcing me to have to re-root. Pretty annoying, and it was odd, since my Nook seemed to be working fine.
Click to expand...
Click to collapse
Mine did this exact same thing too. I messed with the settings apks and then when I went back to the B&N home screen an error about not being able to authorize and the device needed to be reset. then it rebooted and performed a reinstall of 1.0.0
clockworx said:
pokey and I were talking about this in another thread (though he's better at dissecting this stuff than I am). There's a counter for unsuccessful boot attempts, and after 8 it apparently flashes "factory.zip" from partition 3, which is a full clean factory dump.
Click to expand...
Click to collapse
well there you have it. a nice feature, for the reckless
any idea where the counter is kept?
might there be some way to put factory.zip on the SD card, and force a flash? this would just be a parachute in case something gets too messed up for the failed boot counter to work.
This can be done manually too. Look on nookdevs.com for NookColor_UnRooting
Withfeeling said:
This can be done manually too. Look on nookdevs.com for NookColor_UnRooting
Click to expand...
Click to collapse
That isn't the same thing. It only fixes a few things (like Ramdisk, obviously), while this thread is referring to a complete clean /system.
clockworx said:
That isn't the same thing. It only fixes a few things (like Ramdisk, obviously), while this thread is referring to a complete clean /system.
Click to expand...
Click to collapse
actually, in a quiet, unassuming box at the bottom of the nookdevs unrooting page, it does describe a method to flash back to stock. apparently you hold volume down (minus) while powering on. it's easy to miss. i'll break that bit of information out into it's own page.
Ben74 said:
actually, in a quiet, unassuming box at the bottom of the nookdevs unrooting page, it does describe a method to flash back to stock. apparently you hold volume down (minus) while powering on. it's easy to miss. i'll break that bit of information out into it's own page.
Click to expand...
Click to collapse
nookdevs wiki updated:
http://www.nookdevs.com/Flash_back_to_clean_stock_ROM
Given this possibility, is there a way to backup a rooted NC so it would be easier to rebuild after an inadvertant flash.
Some of us noticed that "quiet, unassuming box".
blacter said:
Given this possibility, is there a way to backup a rooted NC so it would be easier to rebuild after an inadvertant flash.
Click to expand...
Click to collapse
This, built-in, mechanism seems like a pretty bullet-proof protection against bricking your Nook Color. The Nook Classic has a similar mechanism. I think it's a great idea and I wish all these new tablets had such a capability.
I'm loving the Nook Color but other things require the money right now so it's going back, for now.
I just did the Home+Power key combination and it did a reset. I re-registered the device to make sure Angry Bird and a few other things were gone and they are. I got a notice at the bottom of the home screen saying something about a software update and it just said I was currently on 1.0.0, I clicked it and it went away. But, in Settings and Device Info there is a Erase & Deregister Device option. When I click the option it says the following "This will remove all digital books and files, including side-loaded content, from this device. The titles you have purchased will remain in your B&N account." I find this interesting since it specifically mentions "side-loaded content" and I'm wondering if this also triggers the 'factory.zip' file and as a complete factory hard reset of files and all. I haven't seen it mentioned anywhere else so I thought it might be worth mentioning.
Cheers
I'm having the same issue as this guy: http://forum.xda-developers.com/showthread.php?t=1156371
I let my nook battery get really low... too low to boot. So, I hooked it up to charge and then it began doing the loop. It comes to the "nook color" splash screen and gets part way through the word "color" when it starts all over.
My question is two-fold:
1) Is there some way to fix this?
2) If the answer to the above is 'no', then how do I boot into Clockwork? It's some combination of holding the 'n' during boot... right?
I've been having this problem too. The way to get back into CWM is to use the rhythm method:
hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long.
Click to expand...
Click to collapse
Now as for fixing the boot loop... I've actually given up on 1.3 manual nooter and gone back to CM7.1 for now... That fixed it, although there are plenty of reasons for wanting stock rooted.
I'm having this issue now. It probably is because I formatted the SD card (if just to make the bloody status pop-up go away...), but I have...well, another problem.
I can't even start trying a fix because I can't shut the thing off. >.> Do I have to wait for my battery to die?
Edit: Got it to turn off (Hold Volume UP+DOWN and Power key), but I can't get it to boot to CWM. There's no 'loading...' screen, just "Read Forever" Then the N screen. =\ I might just act as if I was rooting it for the first time (flash SD card, boot by plugging it in to PC, etc.)
Did you ever get this fixed? I'm having this problem now.
Edit: Nevermind. I wound up wiping and re-installing.
I had a boot loop issue with Manual Nooter. My issue and soln here
http://forum.xda-developers.com/showpost.php?p=19116889&postcount=10
Good Luck.
I've the same problem. It've fixed by:
Right after rooting. Download astro file manager from the market. Go into /system/app and delete Adobe Air, Adobe Flash.
After deleting them .. Just go into Market, download and re-install them again. Should fix your problem.
This boot loop issue has become a serious problem for me. I have re-imaged my Nook Color 3 times, twice with 1.2.0 and once with 1.3.0. All three times the install was successful but upon re-boot I wound up in this loop lock. I got my Nook to run the Kindle android app as most of the technical books that I wanted on the Nook are not available from Dunn and Bradstreet. I've down loaded $350 worth of e-books from Amazon and now I can't download them again. I tied this Flash and Air trick but it didn't fix the problem. So now I've burned $350 in e-books plus the cost of the Nook and memory card. I should have just bought an I-Pad. This is beyond unfunny.
There seems to be some issues with Youtube that can cause this issue. I had to give up on running 1.3 rooted and go to CM 7.1.
It looks to me like the Adobe applications cited above may actually be causing this loop lock problem. With the auto-updates turned off it looks like the loop lock on the Nook Color banner does not occur for a while. Eventually the updates get turned on somehow, and the loop lock occurs. The android OS looks like it's built on a Linux base. I was unable to gain superuser status (perhaps I just don't know how to do it). Without it all I could do was to update Adobe Air and Adobe Flash. As soon as that is done, the loop lock occurs.
Correction to the above comment.
I guess I'm a little brain dead after all this re-imaging. What I meant to say above was the the technical and text books that I was referring to, are not available from Barnes & Noble (not D&B duh!), nor any of their e-book business partners. I would have gladly purchased them from B&N in ePub format.
After putting the Nook Color back to stock condition (1.2.0), I reinstalled the ManualNooter 4-6-16 then immediately attempted the fix recommended above.
In any case, I downloaded the Astro File manager, but since i could not figure out how to obtain superuser status (even with the superuser app) it would not let me remove the two Adobe applications. I could only update them. When they were updated, the banner locked up on the first re-boot. Unlike, the first lock up it displayed the full banner continuously, without completing the boot.
Without source code, it's impossible to tell if there is a bounds problem created by the rooting process, or if this is something else. Someone smarter than I will have to solve the problem.
I think I'm moving on to the less than ideal Kindle Fire, whenever one becomes available. If anyone wants a brand new Nook Color it will show up on e-Bay in a couple of days.
Has anyone here tried rebooting with the sd card removed? This is what worked (previously) for me.
Sent from my NOOKcolor using Tapatalk
---------- Post added at 10:18 AM ---------- Previous post was at 09:44 AM ----------
Now the removal of the SD isn't working... Trying the Abobe AIR and Flash replacement fix mentioned here:
http://forum.xda-developers.com/showthread.php?t=1308304
the adobe air / flash replacement fix worked for me.
I was following these instructions http://forum.xda-developers.com/showthread.php?t=1305891
And under step 3 section where it says create a folder called cminstall, I was unclear if that was on the TP or on my PC. I created it on my pc. I follwed the rest of the steps and when I ran novacom my TP did it's install thing and then at the very end there was a message
"no cminstall dir found, nothing to install.
Power off when ready"
I guess cminstall was supposed to be on the TP. No I can't turn it off. I tried the power button, I tried the power and volume up button, and the center button and the up button, nothing.
Am I hosed? If I can't turn it off how do I web doctor it to get back to webOS?
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
justfor4 said:
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
Click to expand...
Click to collapse
Yeah I just found that button combo on the webos nation forum. Dammit I just made a useless help me thread.
Well, though that this its true, the issue is solved.
And this is thankfully a good thing...
Great
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
lvpre said:
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
VGSmatt said:
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
Click to expand...
Click to collapse
Why don't u test the xronified version? U will be happier
+1 happy user of xronified version
klear72 said:
Why don't u test the xronified version? U will be happier
Click to expand...
Click to collapse
What makes xron better? After only one day, I like cm way more then webos!
Leoisright
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
Too many..or only...Leoisright !!! I've never known anyone who works much as he did and now with the help of MiSfit it will be even better
http://forum.xda-developers.com/showthread.php?t=1321335
What makes xron better?
Click to expand...
Click to collapse
It's faster+beter games support+some fixes like wi-fi. Check benchmarks of cm a3.5 and latest xronified version
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
the rom developer leo has been so enthusiastic and has been pushing updates one after the other in a regular basis and the rom is fast. you will see it when you try it . moreover few more devs have just joined the development which in my opinion is going to make the rom rock
ok before i got to into cm7, i made the jump to xron. You guys were right, its pretty fantastic.
You can't brick your TouchPad.
It's not possible.
Yeah, I may have panicked a little when all the button combos I knew weren't working. Then I found the correct button combo on the webos forum.
I'm having an issue. I was prompted to update to webOS 3.0.4. Long story short after and hour and a half with the black HP screen coming and going I decided something probably wasn't right. I downloaded webOS doctor and am trying to run it, but for the life of me I can't get my PC to see my TP. My PC keeps making the "USB connecting" sounds. I think the problem is that it's looping between the HP logo and total black screen.
F***ing HP and their ****ty software! Anyone have any ideas on what I can do? I've tried holding menu/power and it just keeps looping
Thanks in advance
edit: got it working, here's what I did thanks to webOS support:
Hold power and press center button 15 times. This turns device into a powered off state.
Hold power and volume up to enter USB mode
Download and run webOS doctor.
After about a total of 3 hours of thinking my TP was dead, I kind of have a new found love for it, lol
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
VGSmatt said:
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
Click to expand...
Click to collapse
Xron comes with Gapps but Leo replaced stock browser with Dolphin (which is better). There is a problem if random FCs but they are so much less then what I had in CM7...as Xron is also based on CM7...you will see few bugs...but overall it made my TP so useful..
i agree, this is so much better then before. i don't see dolphin in my app drawer, no matter, firefox is working fine.
yip, it is better and if you want some eye candy the SPB shell 3D is really cool
Q&A for [webOS] [GUIDE] Unbrick the Touchpad
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [webOS] [GUIDE] Unbrick the Touchpad. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
How I fixed mine.
Just made an account to post this if anyone else ever happens to come across this thread.
At first pressing any button combination did nothing. I got the already broken TouchPad from a friend (where he got it from idk) and had no idea what had been done to mess it up, whether it was hardware/software or whatever.
First I tried to turn it on, nothing. So I plugged it in and forgot about it for around 2 days thinking the battery might be dead. I had the stock HP cable but used an iPad brick to plug it in the wall.
After 2 days I held power+home and got the little home button led to flash left and right, but nothing else. Somehow through a series of button holds/presses (power+home, power+down/up+home, etc.) I got the battery with question mark symbol to come up.
Tried holding power+home then power+vol.up again but it wouldn’t go into USB symbol mode
Searched and found jcsullins’ TPDebrick v004 (http://rootzwiki.com/topic/38786-tpdebrick-v004/). I have a Mac but was able to install Linux using Parallels.
Got the “all done” from the debrick program, plugged the TouchPad back into the wall for about a day. Held power+home again, now it didn’t show the battery question mark, but would freeze at the HP logo. Still no luck getting into usb mode and all that would work is power+home to turn it off and on, but nothing I tried would get it through the logo.
Thought maybe I used the wrong storage size in the debrick program (since I had no idea if it was a 16, 32, or 64gb) so I did the 32 instead of 16. Still no luck. Tried 16 again, froze on the logo again. I held home+power to turn it off, then plugged the TouchPad into the wall and it started bootlooping (not frozen) at the HP logo. Okay, that’s at least a difference, but still no usb symbol..
The power+vol.up combo wouldn’t do anything at all, power+home would just turn it off where nothing would work until I did the same combo again and it went back to looping. During one loop I just held down the vol.down button, the thing went off, then I did power+home got it back to looping, then held just the vol.up during one of the loop resets and VOILA! White USB symbol appears and I’m now in recovery mode.
Now I could finally follow this thread (http://forums.webosnation.com/hp-touchpad/320485-how-completely-fix-bricked-touch-pad.html). But had to now install Windows on Parallels (probably could have used Linux but it scares me) to follow the procedure.
But of course Windows couldn’t recognize the TouchPad since I didn’t have novaterm and novacom and the hp drivers etc. I had no idea what any of these programs were so it took a while but I found this thread (http://forum.xda-developers.com/showthread.php?p=20989526#post20989526), got novacom/novaterm, the recovery image, and webOS Doctor 3.00 and 3.04. Followed the instructions there to install the programs, but whenever I tried typing in novacom in terminal I would get “novacom is not recognized as an internal or external command..” Ugh.
This thread (http://rootzwiki.com/topic/6597-installation-help/) said I needed to put acmeinstaller in the same folder as the novacom.exe file in the Palm, Inc folder. So many threads I went to would never have the files I needed or lead to broken websites because of HP discontinuing support, but I was able to get acmeinstaller from here (http://wiki.cyanogenmod.org/w/Install_CM_for_tenderloin) and put it in the Palm, Inc folder. Also found all the webOS doctors here (https://web.archive.org/web/2014021...nals.org/wiki/Webos_Doctor_Versions#Wifi_Only). Terminal still wouldn’t recognize novacom…
So I uninstalled it completely, rebooted, then found this thread (http://forums.webosnation.com/canuck-coding/274461-webos-quick-install-v4-6-0-a.html) and used the WebOS Quick Install tool to get novacom installed and that finally worked. I knew it worked because I checked it with the method here (http://www.reverendkyle.com/index.php/articles/91-problems-with-novacom).
That whole time the TouchPad was still on the recovery mode USB symbol and I was just praying it wouldn’t run out of battery or something while I had to do all that extra searching. So I finally met all the requirements, and was able to successfully complete the process again at this thread (http://forums.webosnation.com/hp-touchpad/320485-how-completely-fix-bricked-touch-pad.html). Followed everything to the dot, copying and pasting lines so I wouldn’t screw up, then the TouchPad rebooted (took a looong time to get passed the pulsing logo though) and sent me to the language selection screen holy crap something actually worked.
Went through the beginning of the setup stuff, but OF COURSE I couldn’t finish setup because HP servers were down, so I couldn’t login or even make a WebOS account. FML.
So I searched and searched and found this thread (http://forums.webosnation.com/hp-touchpad/317164-activation-bypass-touchpad.html) that told me how to bypass the activation. The link in this thread (http://forums.webosnation.com/webos...7-bypass-activation-download-link-broken.html) let me download the tool since the one in the above website was down.
Once I did that the TouchPad rebooted, froze on the HP logo for about 10 minutes, then stayed on the pulsing logo for around 15-20 minutes, then booted to a frozen, inoperable webOS…
Found this thread about jcsullins’ TouchPad toolbox (http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html) So I held power+home, as soon as it started to reboot held power+vol.up and got into recovery mode. Downloaded the toolbox, followed the instructions in the above thread, and was FINALLY able to get it 100% working and on android!
The whole process took me about a week and a day of trial and error since I had no idea what I was doing on 90% of the steps. Everywhere I went people seemed to be saying that the TouchPad was unbrickable and I found it hard to believe, but after going through everything I did to finally get it working it could be true. I feel like I hit every roadblock possible, but at least it paid off in the end. If it wasn’t for all the random advice and success stories I found on various forums I would’ve never been able to do it, so here’s mine hoping it’ll help you! Good luck!!
Alrighty, folks. I've searched the far reaches of the internet, gone through hundreds of pages on this forum alone, and I think I may just have a different set of issues than most.
The symptoms: Long-time thought-to-be-bricked TouchPad with partition for WebOS and Android... Jelly Bean? I think? so long ago... ended up not being bricked, but rather in need of the factory original charging cylinder for proper power flow. When I got it back in somewhat working order, it, PROBLEM 1, got stuck on the Android loading screen (where the word "Android" gets repeatedly swept across with shininess - remember, this is OLD) and never budged from there. I've restarted it who knows how many times by holding down the power and home buttons. I can scroll through the menu with the volume keys, can load WebOS perfectly fine, can launch Android, but it just stays on the loading screen.
Obvious choice is to wipe the whole deal and start fresh. No worries. Except I wanted to get some design sketches off of it, and, PROBLEM 2, my computer was no longer recognizing it as an external drive, or anything, really. I've looked at darn near every "computer won't recognize TouchPad" thread I could find over the past 14 hours. Finally found one with the driver software that could have been my missing link, and my computer won't accept it as a driver. This is a whole other can of worms for someone who has the patience. I will admit that the one fix I haven't tried for this is using a factory original cable. That cable was awful and it broke on me a long time ago. I will try another cable tomorrow, though, as I'm traveling and only have one on me now.
I managed to get my pictures etc off of the TouchPad by booting WebOS and putting it into USB drive mode there (which my computer magically reconizes ). However, I still can't access files in the standard recovery mode to actually do any wiping/software things. I'm well aware that the solution is to go to The Three Dots and switch that developer slider so that my computer knows what's what, but sadly I can't get to the settings menu. There must be another way.
I discovered just a bit ago that I can boot into ClockworkMod; however, I'm not really sure what to do once I'm in there. I can do a factory reset, yes? Would that help?
TL;DR
TouchPad which cannot connect to computer will load everything but Android.
WHAT I'VE TRIED: booting partially through WebOS with WebOS Doctor running and then trying to pick up the connection with TPToolkit when the Dr recognizes the WebOS side of things, new drivers, sacrificing a goat and doing a ceremonial dance around it, etc.
GOALS: Get TouchPad recognized as a USB drive, using ClockworkMod, which is apparently the only thing I have going for me.
Any and all help gratefully accepted. Thank you all in advance!