My Touch Pad went nuts and decided it wasn't going to boot. It will start to boot but only gets to the screen that says loading.. The next screen would be the boot animation but it never gets that far.
I have to hard rest the TP but instead of booting to the Moboot menu it just goes right by and keeps trying to boot cm10. So I stuck in loop hell.
I was trying to boot to recovery but I'm not sure you can without the menu.
Anyone have any ideas? I can get into USB mode but that's it. Haven't tried ADB but not sure if it boots far enough for adb?? another problem is my battery was at 15% so I have to do something fast once I turn it on as it would charge the way it is now.
HELP!?
Hold down a button such as one of the volume buttons while it is booting from a powered down state. Moboot cannot proceed with a button held down. You'll get a prompt to release all keys and you should then go into the moboot menu.
Sent from my slim_tenderloin using xda app-developers app
If you hold the volume up Button and press power till you see tha hp logo, you should go into the recovery mode right away!
pattyland said:
If you hold the volume up Button and press power till you see tha hp logo, you should go into the recovery mode right away!
Click to expand...
Click to collapse
Well that's how its supposed to work. But once I let go of keys it starts to boot into moboot (I can see the screen) but then there is no actual menu and it just automatically starts booting CM10 again.
Anyways I found the ACME un-istaller and was able to run it before my battery totally died (it was at 5%) and at least now I'm back to WebOS and fully charged. I guess I"ll have to reinstall all the Android stuff from scratch. But WebOS isn't all that bad and actually work very well, if only their was app support.
Thanks for your help though.
I am hoping someone can assist me. I have had Android loaded for over 2 years now, and I somehow may have killed it yesterday. Here is what happened. Please help me revive my favorite tablet.
I was going to load Jelly Bean 4.3 and saw in that for most of the ROMs, it recommended to increase system partition to 512 and provided a link. I downloaded the zip file.
I have TWRP, so booted to TWRP and then performed a Factory Reset Wipe, which deletes everything, and is what I do always before a clean install of a new Android version.
I installed the "File to increase partition size to 512".
The next step was to install the ROM, but when I clicked install in TWRP (it is an install program that has some touch capabilities), TWRP just looked back to the home screen, and I go the message:
"No system found". or something similar.
It was in a loop, so I decided to click Reboot to see if I could boot back in to WebOS or my last Jelly Bean version.
When I clicked reboot in TWRP, it said rebooting at the top, but the progress bar didn't move for 15 minutes.
While this was happening, I could not click anything in TWRP, when I touched the Power key, it when to a screen that did nothing, other than let me back to the previous screen if I swiped it, like a confirmation message. It just took me back to the screen where it was locked.
I figured I was well on the way to trouble, so I decided to hard shut down while it was in this state.
I pushed Home, Power, and Volume Up/Down keys until it flickered and the power went off.
Now, I cannot get it to show any life.
I plugged it in and charged it, but still not response.
Can I get it to connect as a USB even though it is unresponsive? Maybe to start over with WebOS Doctor?
Or, is there something else to try?
Please help me, XDA Dev community. I will try anything.
Thank you in advance for your help.
did you find fix
hptjurgensj said:
I am hoping someone can assist me. I have had Android loaded for over 2 years now, and I somehow may have killed it yesterday. Here is what happened. Please help me revive my favorite tablet.
I was going to load Jelly Bean 4.3 and saw in that for most of the ROMs, it recommended to increase system partition to 512 and provided a link. I downloaded the zip file.
I have TWRP, so booted to TWRP and then performed a Factory Reset Wipe, which deletes everything, and is what I do always before a clean install of a new Android version.
I installed the "File to increase partition size to 512".
The next step was to install the ROM, but when I clicked install in TWRP (it is an install program that has some touch capabilities), TWRP just looked back to the home screen, and I go the message:
"No system found". or something similar.
It was in a loop, so I decided to click Reboot to see if I could boot back in to WebOS or my last Jelly Bean version.
When I clicked reboot in TWRP, it said rebooting at the top, but the progress bar didn't move for 15 minutes.
While this was happening, I could not click anything in TWRP, when I touched the Power key, it when to a screen that did nothing, other than let me back to the previous screen if I swiped it, like a confirmation message. It just took me back to the screen where it was locked.
I figured I was well on the way to trouble, so I decided to hard shut down while it was in this state.
I pushed Home, Power, and Volume Up/Down keys until it flickered and the power went off.
Now, I cannot get it to show any life.
I plugged it in and charged it, but still not response.
Can I get it to connect as a USB even though it is unresponsive? Maybe to start over with WebOS Doctor?
Or, is there something else to try?
Please help me, XDA Dev community. I will try anything.
Thank you in advance for your help.
Click to expand...
Click to collapse
I have the same Prob .it will not start did you find a fix? if so could pass it on thanks
Found Fix
I ended up visiting the tpdebrick-v004 thread on rootzwiki. I booted my PC to LINUX 12.04 Live CD and applied the fix. I also ended up charging it for 2 days and it finally powered on. I then did a WebOS Doctor - plenty of instructions on how to do this. Then I used ACMEUninstaller2 to fully remove all Android. Then, I installed the latest CM10.1 with ACMEInstaller5, which automatically increases the partition to 600MB. Took 2 days off and on to do all of this but it worked.
The first step is to charge the battery for 1 full day, then press Power+Home to try to reset. If that doesn't work, try to push Power only, and boot into WebOS if you get this option. From there, you will be ready to start restoring.
If your problem is something other than what I have, the solution that fixes 95% of TP brick problems is tpdebrick-v004 by JCSullins. That should fix you.
Thanks
a fix for hp
:laugh:
hptjurgensj said:
I am hoping someone can assist me. I have had Android loaded for over 2 years now, and I somehow may have killed it yesterday. Here is what happened. Please help me revive my favorite tablet.
I was going to load Jelly Bean 4.3 and saw in that for most of the ROMs, it recommended to increase system partition to 512 and provided a link. I downloaded the zip file.
I have TWRP, so booted to TWRP and then performed a Factory Reset Wipe, which deletes everything, and is what I do always before a clean install of a new Android version.
I installed the "File to increase partition size to 512".
The next step was to install the ROM, but when I clicked install in TWRP (it is an install program that has some touch capabilities), TWRP just looked back to the home screen, and I go the message:
"No system found". or something similar.
It was in a loop, so I decided to click Reboot to see if I could boot back in to WebOS or my last Jelly Bean version.
When I clicked reboot in TWRP, it said rebooting at the top, but the progress bar didn't move for 15 minutes.
While this was happening, I could not click anything in TWRP, when I touched the Power key, it when to a screen that did nothing, other than let me back to the previous screen if I swiped it, like a confirmation message. It just took me back to the screen where it was locked.
I figured I was well on the way to trouble, so I decided to hard shut down while it was in this state.
I pushed Home, Power, and Volume Up/Down keys until it flickered and the power went off.
Now, I cannot get it to show any life.
I plugged it in and charged it, but still not response.
Can I get it to connect as a USB even though it is unresponsive? Maybe to start over with WebOS Doctor?
Or, is there something else to try?
Please help me, XDA Dev community. I will try anything.
Thank you in advance for your help.
Click to expand...
Click to collapse
this worked for my tp good luck
1. Plug the charger in and connect it to your touchpad.
2. Press and hold home+power together for 1 minute. If no response, release, then hold both for 1 minute again.
3. If 2 does not work, keep the charger connected, release the buttons (2) then press and hold home+power+volume up together for 1 minute. Release, then press and hold home+power for 1 minute.
morningforest said:
:laugh:
this worked for my tp good luck
1. Plug the charger in and connect it to your touchpad.
2. Press and hold home+power together for 1 minute. If no response, release, then hold both for 1 minute again.
3. If 2 does not work, keep the charger connected, release the buttons (2) then press and hold home+power+volume up together for 1 minute. Release, then press and hold home+power for 1 minute.
Click to expand...
Click to collapse
If that didn't work, try pressing the power and Up volume button at the same time. This should show the usb logo. Use WebOs Doctor to revive the tablet. This will wack moboot. Use ACMEInstaller 5 on the pc to install moboot (0.3.8), CWM or TWRP zips from the webos /cminstall folder.
Sorry for the possibly FAQ nature of the request. I installed CM9 probably over 18mos on my daughter's Touchpad and was going to update it to JCSullins CM11 ROM. I got all the files downloaded and was getting ready to perform the complete uninstall of CM. Once I rebooted into the moboot 0.3.5 menu I was trying to select the 'boot webOS recovery' option, but no combination of power button + vol up or down seems to do anything except move the menu selection up/down. I can't seem to do anything to actually 'select' an option from the menu. I've tried long press power and short press power both with and without the vol up/down held. I'm hoping I can avoid having to open the unit to disconnect the battery but right now I'm not sure what I can do. Again it's been a long time since I did anything with the Touchpad and when I did the initial CM9 install everything went very smoothly once I got Novacom installed and ran the ACMEInstaller script. I'm hoping there's a simple trick I missed that will help get me out of the moboot screen.
-OK - sorry for the idiot post here, I just figured out the select is the 'front' button on the screen. Feel stupid but got it working! Hopefully I'll have the new CM11 up and running for my daughter tomorrow !
My home button has stopped working on my TP. I'm currently stuck on the mobot 0.35 screen. volume rockers work to move cursor up and down to select webos or Android but home button to select wont work. Seems I can only wait for the battery to die and then let it reboot naturally since holding the power button and the volume rocker doesn't seem to reboot in Mobot screen.
Going forward I'd like to restore home button functionality. it stopped working some time ago. Should I open up HP TouchPad and see if I can fix the issue with the contacts of the home button? Don't know if thats easy or if I'm capable of. Or is there another way to install a newer Android version for me without a functional home button? thx!
Older install methods and iFixit guide
leif2 said:
My home button has stopped working on my TP. I'm currently stuck on the mobot 0.35 screen. volume rockers work to move cursor up and down to select webos or Android but home button to select wont work. Seems I can only wait for the battery to die and then let it reboot naturally since holding the power button and the volume rocker doesn't seem to reboot in Mobot screen.
Going forward I'd like to restore home button functionality. it stopped working some time ago. Should I open up HP TouchPad and see if I can fix the issue with the contacts of the home button? Don't know if thats easy or if I'm capable of. Or is there another way to install a newer Android version for me without a functional home button? thx!
Click to expand...
Click to collapse
Android should be the default boot option for moboot. You could try using the older install methods with the ACMEInstaller5 here if you're desperate to get android working again. Try using a newer rom below.
Download Android 4.4.4 Kitkat install files(Rom, Recovery, Gapps):
Rom:Download the latest Lineage11 build
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-base-arm-4.4.4-20170902-1-signed.zip
Note: Do Not unzip the files.
Repairing the actual button could be tricky but there's an iFixit guide here HP TouchPad disassembly guide on youtube here
Hello and greetings,
I am looking for some help from the gurus here.
I bought this S2 off of ebay, as broken, no power.
plugged in with adequate power supply, the power button was not responding.
I then tried launch recovery mode, and nothing.
Then I found that this tablet would start with download mode enabled.
naturally the battery was flat, but by cancelling download moded, the tablet booted into the system.
the tablet had 5.1.1 and after allowing the tablet battery to charge up to 100%, I then performed a factory reset from within the tablet, and then restarted the tablet to check for issues.
on reboot, the tablet just went black, and again the power button, nor recovery mode would start the tablet, but here i was again able to start the tablet with download mode (cancelling dl mode when initialized).
(i did manage to enter recovery mode, im not sure, i think i was repeatedly trying the button combos and it worked. the recovery menu is untouched vanilla no twrp was installed. i delete the cache, and again performed a factory reset from the recovery console. still, no change in the power button responsiveness from power off)
the next thing I tried was to update the firmware, by grabbing official firmware from updato, and secondarily from samsung-firmware org as a backup source.
both firmwares are official release, 7.0 nougat.
ran odin, and successfully updated the firmware using the file from updato, and the tablet is now running nougat.
everything works great, except when the unit is shut down the power button alone still will not turn the tablet on. (this was the same issue as before i updated the rom to 7.0)
so the next rabbit hole i dug into was creating a bootloader file to see if that would help this issue (extracted the files and compiled into md5 bootloader using Cygwin), the bootloader flashed fine, but still no change to the power button issue. (the Cygwin method can be used to create samsung 4 files repair, but really doesn't do much if you already have the single fat file (firmware))
a couple other oddities:
occasionally the android system installer will go into erase mode, after performing a firmware install from odin, and not complete or reboot.
the system also for the first few seconds after leaving the download mode has graphical artifacts on the screen, just before the samsung logo appears. usually in the bottom half of the screen which are just random blocky colors.
i am pressed for time, and cannot add any more details at the moment, I'll get back later.
any wisdom or insight would be fantastic,
thank you.