hey,
i have a pretty strange problem. My tp was acting up, wasnt showing the softbuttons. So i restarted it. Now i cant use the home button to select to boot into android in moboot. I had that same problem a month or so ago. However the home button started working again after some time.
Ive already waited for 12h and it still doesnt work. Any ideas what to do now?
kingzero666 said:
hey,
i have a pretty strange problem. My tp was acting up, wasnt showing the softbuttons. So i restarted it. Now i cant use the home button to select to boot into android in moboot. I had that same problem a month or so ago. However the home button started working again after some time.
Ive already waited for 12h and it still doesnt work. Any ideas what to do now?
Click to expand...
Click to collapse
Have you booted into webOS to check if you may have a hardware problem?
Is there a method to boot into webos without using the home button? Because i cant select webos in moboot without it.
kingzero666 said:
Is there a method to boot into webos without using the home button? Because i cant select webos in moboot without it.
Click to expand...
Click to collapse
OK I assume that when you reboot your android ROM is highlighted and automatically boots after a 5 second countdown.
With an app such as Rom Toolbox lite select Root browser followed by the boot folder then select the moboot.default file, open it as text and edit it to read webOS(web lower case and OS upper case). Your tablet should now boot into webOS.
If that has worked you now have to be able to boot back into android.
If you haven't already done so DL and install CyBoot or Cyboot from preware and select android for next boot or change the the default.
Have fun.
Thanks for your help. While i was waiting for your reply i opened up my touchpad to check if i can see something wrong, i also cleaned the contacts from the home button board. Well the good news, the home button now works, the bad news my power button doesnt. Guess i screwed it up somehow when opening the tp. fml. Anyways thanks again.
Related
So if you've installed recovery, you probably have realized that timing is everything on going into recovery. It can be a down right pain in the butt to get that key combo working. To make matters worse, you go to plug it into USB so you can run ADB in recovery, and the phone starts booting itself! Then comes the battery pulling so you can ensure that it will actually take your key holding. Any of you that use recovery a lot know what I'm talking about.
I discovered a solution for this called "Quick Boot." You can get it here: https://market.android.com/details?id=com.siriusapplications.quickboot&feature=search_result (it's free for regular version)
If you're already booted and want to go into recovery, fire up this puppy, select "recovery," and before you know it, you're there.
This has the added benefit of not asking you to hit the confirm wipe in order to get into recovery!
I know it's a minor thing to address a minor pet peeve, but I'm just throwing it out there as I found it really convenient.
Should be very handy till we get roms that have this tied into the power button
does this change the shutdown menu to like that in CM7? I ran CM7 on my Eris before I got my Revo and I loved the shutdown menu!
Jasbo said:
does this change the shutdown menu to like that in CM7? I ran CM7 on my Eris before I got my Revo and I loved the shutdown menu!
Click to expand...
Click to collapse
Its somewhat like CM7's menu. When you click it a menu opens with similar options as CM7 ie.. reboot, recovery, power off. Hope that helps?
This is a great find Major...
Perfect, thanks.
Awesome! Thanks for this app!
bwhxeon said:
Should be very handy till we get roms that have this tied into the power button
Click to expand...
Click to collapse
I'm running Revolt 1.3 and it has the recovery option in the power button. Still an awesome ap for those running stock rooted without the power button option.
I'm using Windows Vista Home Basic to install CM7 to my Touchpad. I've followed all of the steps for installing CM7 to the point where you enter this
Code:
novacom boot mem:// < ACMEInstaller
from the command line. It accepts the command but then nothing happens. It's been sitting there for an hour and now I can't turn off the Touchpad to reboot. The USB symbol is sitting in the middle of the screen and nothing I do seems to affect it. Even tried pressing the reset button through the tiny hole but still nothing. Have I bricked my touchpad?
No, hold the home+power buttons to force a reboot. Your PC probably won't work, as i had to try 3 different ones. Ended up working on 32bit Vista. Also, uninstall old versions of Java, and only have the newest version.
Sent from my Legendary 2.2 infused device.
lewmur said:
Even tried pressing the reset button through the tiny hole but still nothing. Have I bricked my touchpad?
Click to expand...
Click to collapse
You mean the microphone hole?
Like Zanderman said, hold power + home until it reboots. It feels like you gotta hold it for a long time but I say about 15+ seconds should do it.
Also, make sure you have the novacom drivers installed correctly.
mountaindewmi said:
You mean the microphone hole?
Like Zanderman said, hold power + home until it reboots. It feels like you gotta hold it for a long time but I say about 15+ seconds should do it.
Also, make sure you have the novacom drivers installed correctly.
Click to expand...
Click to collapse
I always get in trouble putting things in the wrong hole! Used another laptop and got it to install.
lewmur said:
I always get in trouble putting things in the wrong hole! Used another laptop and got it to install.
Click to expand...
Click to collapse
LOL... I read the same thing on the iPhone 4 forums about sticking things in the noise cancellation mic hole. Glad u got it working tho!
I bricked my touchpad.
First I installed cm7 alpha 3.5
It seemed working fine except wifi.
It got connected but once I rebooted it, it dropped the signal.
It ketp scanning the wifi signal so I just decided to install cm9.
I downloaded cm9 and put it in a folder named install.
I booted into clockworkmod and wiped data and all caches and flashed it.
Guess what?
I rebooted and the screen is just black.
I can see there is backlight but nothing comes up on the screen.
I just let the battery drain for a couple of days, and charged it.
still same thing. nothing comes on. Charge battery sign came on after I drained the battery before I plugged the charging cable in.
home button + volume button + power button = does not work.
What should I do?
My PC does not even read it when I connect it with USB.
I need help from you guys.
Firstly, I know exactly where you ran into your problem. You ran the upgrade from CM7 to CM9 from CWM. It explicitly states it in the instructions that you are NOT supposed to do that.
So, what I would do, if I were you, is try the following:
From when it's on, press and hold Power + VolUp, then hit the Home button 10x in fast succession. Then let everything go until the the screen shuts off. From there, press and hold Power + VolUP, you SHOULD end up with the big glowing USB symbol. This is where you wanna be. If you can get there, then you can run the AcmeUNInstaller, and remove the CM7 and CM9 install stuff. From there, you reboot into WebOS, and put the CM9 install stuff into the /media/cminstall folder, and try to run AcmeInstaller2 (very important to use 2, not just Installer). That'll allow you to install CM9.
If you can't do that, there's a thread at http://forum.xda-developers.com/showthread.php?t=1426244 that shows how to completely remove Android from your Touchpad, restore it to WebOS 3.0.0, and then upgrade from there. It's the best option, I think, if you can't get the AcmeUninstaller to work.
Hope that helps, mate.
Thank you.
I will try it and post.
Thanks a lot..
hopefully everything goes well...
It worked
I unstalled cm7 and other related files.
Thanks a lot!!!
I have a 32gb Touchpad. It has been running CM7 fine (dual boots that and WebOS) since June 2012. The battery had completely died so I plugged it into the power adapter. After it had charged for a few minutes it started to go threw the process of loading. The hp logo came up as normal and then a black screen appeared with the message "Please release keys..." I tried keeping the power button pressed down for eternity does nothing (I've rebooted if the Touchpad has gotten frozen before or if the touchpad didn't recognize touch on the screen).
Please help, I have no clue what to do. I googled the problem and it seems people have this happen when they install CM, but mine's been running fine for months and this is spontaneous.
Sounds like your home key is stuck!
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
Sounds like your home key is stuck!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Any suggestions on how to fix this? Although it doesn't seem to be stuck. I am able to press it when trying to reset the device.
Touchpad Boot Loop due to Stuck Home button
-SGA- said:
Sounds like your home key is stuck!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I think this is what I have been experienced :
Have done some significant research before posting but have not found a clear match to my problem. I bought two Touchpads for my daughters when on fire sale (lucked out with OnSale), and they have been running with CM9 with no problem for several months. One of them last week would not boot and after some charging it appears to be stuck in a boot loop. I have charged it for several days to try to eliminate battery issues with no luck, and I suspect something other than charging...
Here is what it will do :
If I hold home and power to reset, it will momentarily show the HP logo, then the Moboot menu, but it instantly flashes to a Cyanogenmod boot with no waiting (first clue that the home button is stuck ????). The unit then tries to boot but the display will not stay lit. Occasionally when the unit is resting on the Touchstone I can see the clock like it has been booted into CM9, but I cannot interact with the touch screen at all, and the clock will not stay on the display.
If I try to boot and bring it into recovery mode, I can hold the Volume Up after releasing the home and power and I get a blue screen and the message to "Please Release Keys" (another clue that the home key is stuck ?).
From this position it runs the boot loop again, with no opportunity to interact. Can't get it to recovery so it is a paperweight at this point..
I see my options as follows :
1. Keep trying to charge to see if it is just a battery charge issue, but if I see evidence that it is booting into CM9, that steers me away from this solution
2. Let it discharge cpmpletely and then recharge (don't really like the risk of introducing a battery issue where there isn't one...)
3. Crack the unit open and try a replacement of the home button
Would appreciate any input.
Thanks
Todd
You might try using adb.
In the terminal navigate to the folder with adb and:
adb start-server (to start adb)
adb devices (to confirm the Touchpad is recognized)
adb reboot recovery (to boot into recovery)
adb reboot recovery should be entered while it has the boot loop in process
Sent from my SAMSUNG-SGH-T989 using xda premium
thanks for the reply. Installed the SDK and ran ADB,but it does not recognize the Touchpad - have tried reset, all manner of button combinations and it won't list it as a connected device.
Any other ideas ?
Thanks in advance
Todd
-SGA- said:
You might try using adb.
In the terminal navigate to the folder with adb and:
adb start-server (to start adb)
adb devices (to confirm the Touchpad is recognized)
adb reboot recovery (to boot into recovery)
adb reboot recovery should be entered while it has the boot loop in process
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
cthenrys said:
thanks for the reply. Installed the SDK and ran ADB,but it does not recognize the Touchpad - have tried reset, all manner of button combinations and it won't list it as a connected device.
Any other ideas ?
Thanks in advance
Todd
Click to expand...
Click to collapse
I don't think that your home button is stuck. If it were stuck, the screen would read "please release keys" as you have seen when holding the volume buttons while booting. Based on that, I wouldn't suggest attempting to replace the home key.
It's likely that debugging was not enabled on the Touchpad before the issue started, hence why adb cannot connect, which is unfortunate.
I would suggest that you might try pressing one of the volume keys in rapid succession while booting into moboot. That may get you the opportunity to catch the boot menu before the timeout (sounds like it has been set to "0" somehow).
Well I got it to do something...
I got it to where my PC would recognize a Palm / Novacom device and was able to run WebOS Doctor, which is great. What is not so great is that I get no display, although I can tell the unit is booted into WebOS (I.e. I get a tone when increasing / decreasing volume and I can get the camera to fire by pressing power and home.
After a reset and putting it on the touchstone it appears that WebOS is running fine, but there is nothing on the display.
Best guess now is just a bad display that can be replaced,correct ?
Thanks for the help
Todd
-SGA- said:
I don't think that your home button is stuck. If it were stuck, the screen would read "please release keys" as you have seen when holding the volume buttons while booting. Based on that, I wouldn't suggest attempting to replace the home key.
It's likely that debugging was not enabled on the Touchpad before the issue started, hence why adb cannot connect, which is unfortunate.
I would suggest that you might try pressing one of the volume keys in rapid succession while booting into moboot. That may get you the opportunity to catch the boot menu before the timeout (sounds like it has been set to "0" somehow).
Click to expand...
Click to collapse
Hi all. I have this old Touchpad that's been sitting in a drawer for years now. I shelved it because I could no longer boot android on it. It would hang with the android logo and stay that way till the battery died. I opened it today to take a look at resetting it because I want to get it going again. I discovered a little button on the board that resets the touchpad. Now I don't have to wait till the battery dies to try something different.
I can get it to boot to moboot 0.3.8 from there I can move the selection thing up and down to select a different boot choice but I don't know what to press to get it to boot that option. I thought it was the home button but that does not work. I would like to wipe it clean and start with a recent ROM that is solid and fast.
What's the first thing I need to do to get away from the moboot screen?
Jonathan
Ok I got past that by long-clicking the home button. Now i'm at the USB logo. I guess I can probably figure it out from here. Any pointers welcome though.