Hey guys,
Hope someone knows anything about the issue I'm experiencing. I downloaded all the files for the install from liliputing ([h t t p : / / liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html)
I installed the files as the website says, but I believe the wire from my laptop to the touchpad became loose very deep into the install. At which time the touchpad went black, rebooted and showed the menu for booting into webOS or android. When I let it load android the little android baby face comes up for 5-10 seconds, then restarts back to the boot menu.
This was tried with the latest update with bluetooth experimentally working 4.2.2. I also tried the older update from 12/12/2012 with audio and video working.
Does anybody know best solution? Factory reset my touchpad and try from scratch? Wasn't sure if its novacom on my desktop messing up. Should I uninstall and reinstall?
Any help is appreciated!!! Thanks!!
em11488 said:
Hey guys,
Hope someone knows anything about the issue I'm experiencing. I downloaded all the files for the install from liliputing ([h t t p : / / liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html)
I installed the files as the website says, but I believe the wire from my laptop to the touchpad became loose very deep into the install. At which time the touchpad went black, rebooted and showed the menu for booting into webOS or android. When I let it load android the little android baby face comes up for 5-10 seconds, then restarts back to the boot menu.
This was tried with the latest update with bluetooth experimentally working 4.2.2. I also tried the older update from 12/12/2012 with audio and video working.
Does anybody know best solution? Factory reset my touchpad and try from scratch? Wasn't sure if its novacom on my desktop messing up. Should I uninstall and reinstall?
Any help is appreciated!!! Thanks!!
Click to expand...
Click to collapse
First off you did it wrong! that's a guide to run cm9 not cm10 just like how you ran acmeinstaller you have to run acmeuninstaller. if you don't have that then you need to download it and place it into the palm, inc folder that you have acmeinstaller in. Then go back step by step you have to download cm9 first! load cm9 then after cm9 is installed boot back to webos open cminstall folder drag and drop Android 4.2.2 with the correct gapps Idk which android 4.2.2 your running but I'm guessing cm10? Then boot back into moboot, toggle to clockwork mod then toggle to install zip from folder then toggle to cminstall then open android 4.2.2 zip after that install gapps and then restart then voila android 4.2.2 hit the thanks button
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Related
Hi guys i been searching everywhere, all over forums and google and i cant seem to figure out this issue, the issue is that i have a demo version of a 32gb touchpad, and basically i followed all the steps to install clockworkmod and moboot and all that stuff, once all that was completed i choose to install an android rom from the development section, and no matter what i do in clockworkmod, it just keeps restarting, it begins installing a rom and then just automatically restarts. it does that when i wipe cache aswell, i redid the entire process again and i get the same issue, everytime i try to install a rom or do a gaaps update it just restarts and nothing gets installed, Please let me know how to fix this issue
Sounds like you need to completely restart fresh. It could be because of the Demo setup of the TP, it doens't wanna allow CWM to work properly.
What I would do is read THIS THREAD and follow the instructions - it'll factory reset everything, but it'll then be ready for you to install CWM, Moboot, and CM9 again. I know it works cuz I just did it last night.
thanks alot buddy, it WORKED!!!!! now my touchpad finally has android, and webos, oh man android is amazing, my kid luvs it
I tried searching but can't find any solutions to my question, so here goes.
I uninstalled Android because I was getting random reboots. When I tried to install it again using ACMEInstaller3 it got stuck because it couldn't find the CMInstall folder. I tried doing the hard reset but it just says the buttons were pressed on the linux lines. Any help would be much appreciated!
disguy03 said:
I tried searching but can't find any solutions to my question, so here goes.
I uninstalled Android because I was getting random reboots. When I tried to install it again using ACMEInstaller3 it got stuck because it couldn't find the CMInstall folder. I tried doing the hard reset but it just says the buttons were pressed on the linux lines. Any help would be much appreciated!
Click to expand...
Click to collapse
never experienced that issue, maybe just wait until your battery dies (will happen eventually) and then try to reboot into webos creating a proper cminstall folder?
liquidor said:
never experienced that issue, maybe just wait until your battery dies (will happen eventually) and then try to reboot into webos creating a proper cminstall folder?
Click to expand...
Click to collapse
Press the power and home buttons for as long as it takes, shouldn't be more than 30 secs and it will turn of .
You do not want the battery to totally drain as this will cause even more problems.
do you have moboot and cwm recovery installed properly? if you have cwm installed then yuo can just flash the the rom from there.
So being the airhead I am I let my hp touchpad run out of battery. I charged it and when there was enough juice for it to come on(witch it does automatically) then it went to mooboot, a blue cyanogen mod robot face came on, and after a couple of seconds the screen just goes black, the screens on but black. I let it sit on the charger for a while and then it rebooted itself and did the same thing again. It has not restarted its self since then so I do not think it is a boot loop. anyways I let it boot up in webos so it could charge up to 100% in peace hoping that would solve it, but it did not. So basically webos runs, clockworkmod recovery runs(idk how cwm got on I like twrp better) and I can boot it into the webos recovery(big ass usb symbol). It was running the latest stable cm 10.2 I believe. I actually would perfer to run cm 10.1 because it has bluetooth and is compatible with minecraft pe. If you have any suggestions I would be very graitful. Also if we can avoid phoenix suite that would be preferable because I have a windows 8 laptop that is not very friendly towards that program, if I have to use it, thats fine.
rootedbuddha said:
So being the airhead I am I let my hp touchpad run out of battery. I charged it and when there was enough juice for it to come on(witch it does automatically) then it went to mooboot, a blue cyanogen mod robot face came on, and after a couple of seconds the screen just goes black, the screens on but black. I let it sit on the charger for a while and then it rebooted itself and did the same thing again. It has not restarted its self since then so I do not think it is a boot loop. anyways I let it boot up in webos so it could charge up to 100% in peace hoping that would solve it, but it did not. So basically webos runs, clockworkmod recovery runs(idk how cwm got on I like twrp better) and I can boot it into the webos recovery(big ass usb symbol). It was running the latest stable cm 10.2 I believe. I actually would perfer to run cm 10.1 because it has bluetooth and is compatible with minecraft pe. If you have any suggestions I would be very graitful. Also if we can avoid phoenix suite that would be preferable because I have a windows 8 laptop that is not very friendly towards that program, if I have to use it, thats fine.
Click to expand...
Click to collapse
Get the most recent version of the TWRP zip and put it into the /cminstall folder in WebOS. If you don't have the latest version of moboot (0.3.8) then put that zip in cminstall too. Run the latest version of ACMEInstaller using the appropriate script for your ROM version from your PC. That script should uninstall CWM and install TWRP. If you still have no joy then put the latest ROM and appropriate gapps zips into cminstall and run the script again. Clear the cache before rebooting into android.
Hope this helps.
I've had this issue before. All I did to solve it was to reflash the rom from recovery menu.
That should be all it needs. Its worth trying first before acme, etc etc.
Peace
http://forum.xda-developers.com/showthread.php?t=2712680
THX everybody to take a look. I've flashed the 04/09 version of KK under Jcsullins's project. Thx a lot for his hard work. But I have a problem that everytime I boot the device, in the left down corner, it says "safe mode". What's wrong? Is this just like the windows safe mode & hardware doesn't work fine? How to quit this mode and use KK correctly? Just, please helllllp, thanks.
During first boot of KK, touch screen is not working until I press power button twice. Is this a hardware issue or the step of my operation? By the way, WIFI couldn't be opened. I flash webos 3.0.5 using webos doctor and then perform an full reset, then install CWM&moboot using ACMEInstaller5. Then in CWM i flashed the 32G partition zip file and everything seems fine. Then the rom flash, reboot, that's it. Weird. Is the step for me wrong?
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
josh426 said:
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
Click to expand...
Click to collapse
I have heard no reports of what you describe.
I suggest using TPToolbox v41 from here (download link in that post):
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
and try again.
If it does it again, I will need to see a kernel log file to help diagnose what's happening.
To get that, following the instructions on this post:
http://forum.xda-developers.com/showpost.php?p=53258228&postcount=10
but replace steps 1-3 with:
1) Load Touchpad Toolbox
2) Start holding the Volume Up button
3) Continue to hold VolUP until you see the big USB symbol (i.e. webOS recovery)
Errgghh
Downloaded but not sure what is going on. I think the problem my be with something being overwritten during one of the first attempts. With the USB logo displayed, I connect it to the PC. The minute it starts to transfer, it resets and I see the hp logo and then the boot screen. At this point it is stuck in a rebooting loop for several times. I even just tried webos doctor and it starts at 1% and as soon as it hits 2% it reboots the same way.
Also will not mount as a USB drive on the PC. Just as a palm noobie or something so I can not access anything on the device manually.
While I have not experience your issue I have had other issues that were resolved by changing to a different USB cable. Might be worth a try.
Sent from my MT2L03 using Tapatalk 2
Having the same issue. From USB to HP logo, then 1.5 seconds of text and then reboot. Tried V41 and V42 and tried multiple USB cables.