Database Develop

[Q] rooted OK but now it continues to try to boot

I rooted my NC yesterday using the auto-nooter 2.12.25. Things seemed OK. I DLed some apps & used them. Got ADW launcher loaded and began setting it up for my preferences. The NC went most of the way through an update cycle even though I had already updated to version 1.0.1. However this time it never got to the green "n" and then it started cycling through the part where it comes up & writes "nook color", continues until the colors quit flashing & then starts back at "nook color".
None of the buttons seem to have any effect. I tried to follow the 'solution' entitled "NookColor Fix Boot Loops". I tried both the auto-nooter SD card and then when that didn't work, I tried the original manual nooter SD card.
Anyone have another idea to fix this. I'd really appreciate some help. A PM would be great or just answer here.

I had the same problem earilier today, I held down the power button until it did a complete reset (about 8 seconds of holding). It is working great since.

Thanks. I had already tried that, several times.

restore to factory and start again?
add http : // www to front of links with out the spaces i don't have the 8 post count needed to post links and
am not going to just reply needless info to 8 post to get rights to post links to help
don't get me wrong i believe it is a very good policy
unrooting
.nookdevs.com/NookColor_UnRooting
flashback to clean stock
.nookdevs.com/Flash_back_to_clean_stock_ROM
i have not tried any of these methods no need to but i do so much messing up
i guess eventually i will with that said this might be a long way around to your solution
read both carefully

Thanks, nookroot but this is not working.
Method 1 for unrooting - Holding those 3 keys together for over 30 seconds has no effect.
Method 2 for unrooting - I can't unroot with method 2 because the NC has to boot before I can go to settings.
Any other suggestions? In fact it seems that if it ever does power off, the only way to make it power on is to plug in its USB cord & this doesn't always work. When it does it just stats cycling. Sometimes it seems to just power up on its own and start cycling.
Whatever happened, since it's rooted I can't return it to B&N and I don't seem to be able to unroot it. Effectively I have bricked it even though many people say that's impossible.
Edit: something new just happened & I was able to go through the method 1 reset. It's booting now & looks like the B&N screen is coming up. I'm not sure how it happened. I'm going to leave it unrooted until I feel adventurous (or foolish) again.
P.S. Came back with version 1.0.0 SW.

[Q] Semi Bricked?

I've got an 896 Rogers Captivate that has been draining my sanity for hours now.
I managed to get it to download mode exactly ONCE out of ... literally eight hours of hold buttons, remove battery, replace battery, hold buttons, remove battery, etc etc.
I reached download mode by using the three button technique Volume Up + Volume Down + Power.
Once there I idiotically said "I can get here again.." and removed the battery.
I got this phone from a family member and managed to get it to download mode, but every other time I hold buttons (any buttons) it does exactly this:
If plugged into the computer it shows the loading daisy (which doesn't animate). I can hold any combination of the volume buttons and power button and it will flash black and return to the daisy.
If not plugged in, it shows the model number and 'Samsung'. Behavior is the same. Holding volume up, or down and the power button will flash black after eight seconds and then show the model and 'Samsung'.
I haven't tried Odin (although I've downloaded it and a rom thusly), a Jig, or any of the other brute force approaches to reaching download mode simply because I know that if I reached there once, I should be able to reach there again. Computers aren't sentient (although I swear this phone enjoys tormenting me).
Does any body have any insight to why I would be going through this?
Why won't it reach download mode again?
Just fyi: I have literally tried every button combination I can suss from the countless threads I've scoured and scanned.
Thanks in advance for any insight anyone can provide.

Just to make sure, as I didn't see it in the post, you did do v+/v- and insert the usb cord from a powered off state, right?
Also, check the captivate connection issues thread in my signature if you haven't already.

Different reaction
Hey thank you! Your list is handy!
I'm shocked I hadn't stumbled upon it already, or your signature for that matter..
Seriously can't understand how this is the first time I've seen it.
I've tried the [FROM A POWERED-DOWN STATE - BATTERY REMOVED] procedures but none of them got me into download mode.
Thanks all the same.
I'll try the battery charging list next.
Quick (and possibly stupid) question : Does it matter if it's an official Samsung USB cable?
As I noted in my initial post, I managed to get into download mode earlier today (little Android digging my grave with the same cable I've been struggling with for the past six hours.

Luck!
omigodomigodomigodomigodomigodomigod
okay, so I managed to get into d/l mode by plugging to power (outlet usb) and then applying three buttons.
So:
Battery Out
Plugged into USB
Battery In
Hold VolUp+VolDown+Power
Android man digging my grave showed up.
It should be noted that this same process was conducted several times against my PC upon which the technique worked several hours (and several hundred attempts, and half a season of StarTrek TNG) ago.
...now what (lol!)
I guess I'll fire up Kies and conduct a few more hours of scouring!

well you COULD go about flashing roms and kernels and modems to your hearts delight. But I would advise against that. I'd recommend first backing up EVERYTHING. Especially your /efs (you'll need to be rooted) folder if your considering flashing a rom. Once you do that you're free to flash. Just be sure to read the OP of the rom to make sure you meet the requirements for the rom or kernel, such as if you have the right boot loaders. As long as you read, you really can't go wrong with the captivate.
Sent from my SGH-I897 using XDA App

I'm not entirely sure how the phone reached this state but according to all the stuff I've read, if the phone is in this state it's recoverable using Kies.
However Kies doesn't seem to care that I've got this phone plugged in.
Frankly, there's nothing to back up, and if flashing out with Odin is the only way to establish a working Captivate then I suppose i've got some files to download.
Does anybody have any insight regarding Kies and getting it to play nice nice?

Do you have Samsung drivers installed?
Personally, I have only got Kies to work when the phone was actually on.
Sent from my SGH-I897 using XDA App

If your in download mode, I suggest just flashing back to stock using heimdal.
(I don't use odin 1-click stocks because my first attempt at using it corrupted my bootloaders. My phone would power on, go through the AT&T screen for hours. I also could not enter recovery or download using 6 different methods including a jig. I lost hope and accidentally left my phone on when I went to bed. I wake up next morning and it booted up. I used terminal emulator from the market and used the command Reboot Download. I worked, then I flashed back to stock using hiemdal. I am not completely sure why I shared this story but w.e )

Bricked Touchpad need help

I have been running CM9 nighties for some time now with no issues on my 16GB US WiFi only Touchpad. I installed TWRP and after some time decided to remove it and just use CWM. After trying several things from the posts (which would not work) I decided to remove CM9 completely then reinstall. This is where I got into trouble...
I loaded all necessary CM9 files in the cminstall folder on the Touchpad. I successfully ran ACMEUninstaller and got back to the WebOS language selection (i.e. the initial WebOS screen from factory). Instead of logging into WebOs (felt there was no-need since I never use it), I put the unit in Download mode (vol down + power). I then ran ACMEInstaller2. I received an error (text on the black touchpad screen which I assume is the bootloader) saying the needed files were not installed and something like "remove the wall". I thought I would reboot the unit and now log into WebOS and reinstall the CM9 files (thinking I made a typo when loading them). Now I cannot get the Touchpad to reboot - totally black and even when connected to the PC I dont get the USB connection sound.
Does anyone know if there is a hardware method to bring the unit back (maybe a different sequence of button presses or shorting a pin on the USB connector)? I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port.
Any thoughts would be greatly appreciated.
EDIT
Resolution: In a post I saw dated May of 2012, the user indicated HP was still honoring their warranty. I contacted HP via their Chat service, after giving them my model and serial number, I was told I had three weeks remaining on my warranty. HP sent me the return box with authorization and in a week I received (what seems to be) my exact Touchpad... only now it booted just fine. I have since reinstalled ICS and am running fine. Thanks to all who responded. I wanted to share this as I am extremely impressed with HP's warranty service (no questions were asked if I had rooted the device, where I bought the device, etc).

Make sure that your touchpad is not low on battery and see if anything happens when you plug it into the wall charger that it came with.
This has almost been the problem for me when my tp has problems.

Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is.
paul96 said:
Make sure that your touchpad is not low on battery and see if anything happens when you plug it into the wall charger that it came with.
This has almost been the problem for me when my tp has problems.
Click to expand...
Click to collapse

[Q] hp touchpad...sorry too many cards!

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

TouchPad won't load Android, not recognized as USB, ClockworkMod and WebOS work fine.

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!