Related
So I've come here as a last ditch effort
I've been trying to load CM9 onto my tablet for several days now and am having absolutely no luck. There are always two things that happen with it either it constantly reboots on the loading screen right after the splash screen or if I somehow manage to get past the loading screen, which has happened maybe a half dozen times it reboots after I hit one or two buttons.
Now as far as I know I've tried every single way of flashing the roms.
I've used ACMEInstaller2
I've used ACMEUnInstaller, then ACMEInstaller2
I've used cwm and twrp to flash (I wipe data, cache and dalvik everytime)
I've flashed CM7 and then ACMEInstaller2 CM9 on top
I've flashed CM7 and cwm to flash to CM9
I've used the uImage cleaner in cwm then wiped data, cache, dalvik and reformatted data, cache, and system, reflashed and wiped cache/dalvik again and fixed permissions
I've tried multiple Roms including but not limited to Classicnerd, CM9 alpha 2, and CM9 nightly.
They all end up with the same issue
Note:I've also applied the various reboot fixes, and none of them seem to make a difference.
I can get CM7 to work on the tablet in the effect that it runs smoothly once it starts up but it does do the loading screen reboot quite often and the only way Ive found around that is to wipe the cache/dalvik every time I start up the tablet.
If anyone has any ideas of where I could go next with this it would be greatly appreciated, I'm pretty much at my wits end lol.
Edit: Oh I forgot to mention I've also WebOS doctored it.
What version of WEB OS doctor did you use? And have you tried formatting the SD card option in web os?
I used webos doctor 3.0.0
Also I was told not to format the sdcard, is it just the option in cwm or do i go about doing that another way.
In web os you have the option to format the memory card. But if you doctored with 3.0 you should be fine as it re partitions the device before formatting and flashing.
Hrm, well if I got the right WebOS doc any other ideas that might work?
Have you tried a full factory reset ? Using THIS THREAD, you can wipe everything back to complete nothingness, then try reinstalling. It could be something is wrong with your boot entries, partition table, or the like. I know you've tried to doctor it, but doing it this way ensures you start with a completely clean slate (to the point of deleting all of your partitions and starting fresh).
Back up anything you wanna keep, then try that - and re-download all of the necessary files again, just to be sure. It's what I would do.
Check that its charged.
My tp will reboot at the splash screen if charge is <70%. Only booting to webos whilst connected to charger, then leaving for a day will allow it to boot reliably to cm9.
Even on the latest nightly, I have big charging issues with cm9
Sent from my cm_tenderloin using xda premium
Well I did the factory reset as you suggested and then doctored it from 3.0.0 to 3.0.4 then tried CM9 again-No Change. So I decided to flash CM7, which seems to run fairly stable it I think I've only seem it reset once and as for the rebooting after the splash screen it still does that but if you let it restart a couple times it eventually goes through. I downloaded a CPU overclocker and set the min to 384 then reflashed CM9 through ACME. It seemed to work for awhile, about half an hour, watched an episode on netflix then when I tried to open another app BAM reboot and now its back to either loading screen reboots or about 5 seconds worth of CM9 then reboot. This has got to be the most frustrating piece of equipment I've ever worked with.
That's really odd... Especially since it worked for a bit and then not. Is it getting overly warm ? That might be a sign of an overheating problem. Or you could just have a bad device. They do exist. Does it do the reboots from within WebOS as well ? Or just when you're on Android ?
No its never rebooted in webos. And it doesnt feel like it was getting hot, when I was checking the CPU stuff it was running at around 27 degrees celcius I believe I'm not sure whether thats overly hot or not.
Update: I ran the tablet again and it seemed to work pretty stable for about 10 mins then random restart I had the cpu temp up on the main screen though and it read 22 Celsius before it rebooted.
Restart Problem
I have had touchpad for 8 months after which the screen did not respond to the touch. So I sent it for RMA and received another unit. I installed the aplha2 but it kept on restarting as soon as I boot into the Android. I tried different ROMS's as well but same problem.
I downgraded the webos with webos doctor 3.0.0 but the same. No matter how I use the touchpad in webos it does not reboot.
Any help will be much appreciated.
Thanx
kenbhaji said:
I have had touchpad for 8 months after which the screen did not respond to the touch. So I sent it for RMA and received another unit. I installed the aplha2 but it kept on restarting as soon as I boot into the Android. I tried different ROMS's as well but same problem.
I downgraded the webos with webos doctor 3.0.0 but the same. No matter how I use the touchpad in webos it does not reboot.
Any help will be much appreciated.
Thanx
Click to expand...
Click to collapse
WebOS doctor back up to 3.0.5
AcmeInstaller2 to install one of the latest nightlies (alpha 2 is quite outdated which a search would have revealed)
If you still have issues you may be one of the unlucky few whose Touchpad hardware just won't tolerate Android to which there is no fix
Sent from my cm_tenderloin using Tapatalk 2
Replacement?
Thanx for replying. Is there any way that I can get it replaced since it is under the warranty of course I wouldn't say that it reboots in Android but can I make some excuse to get a replacement which may turn out to be good device?
A week ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
ss0198 said:
A weekhttp://goo.im/devs/jcsullins/cmtouchpad/testing ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
Click to expand...
Click to collapse
Try leaving the tp charging, at least overnight, till it's 100% charged. Then try the guide again. If you're having trouble with novaterm, there's a good work around on page 12.
If you're having trouble with the doctor, either the 8% or the 12%, do a search for either. Don't worry, there's a workaround. Also search the webos nation forum, you'll find answers there also.
Good luck.
Edit : use cwm. Myself and several others here have had problems with TWRP.
Here's the link for cwm : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Use the 12/15 one.
AW: [Q] HP Touchpad no longer booting.
I already that, but it only charges until it tries to boot.
Are you using the cable that came with the TP?
AW: [Q] HP Touchpad no longer booting.
Yes.
AW: [Q] HP Touchpad no longer booting.
The problem is, that it tries to boot, but it can't boot.
Have you tried to power it down whilst still plugged in ?
AW: [Q] HP Touchpad no longer booting.
What do you mean with:
sstar said:
Have you tried to power it down whilst still plugged in ?
Click to expand...
Click to collapse
What I mean is you have your TP charging and it automatically boots when it has sufficient charge, while leaving still connected to the charger have /can you turn it off but leave it connected?
AW: [Q] HP Touchpad no longer booting.
I will try it now.
AW: [Q] HP Touchpad no longer booting.
I just tried it, but it instantly reboots after turning it off.
It's obviously stuck in some sort of loop, my final thought is to hold both power and volume to put it into recovery and leave it so that it hopefully continues to charge .
You said you had a problem with running chicle's suggestion with the restore your TP to factory condition, how far did you get ?
AW: [Q] HP Touchpad no longer booting.
I alreqdy tried to charge it in recovery mode, but the battery didn't charge either. I tried to reset it with serval versions of the webosdoctor, but as I said it didn't work. It just said it couln't reset the phone. In the console/log it crashed at charging. And it list connection.
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
sstar said:
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
Click to expand...
Click to collapse
Yes.
ss0198 said:
Yes.
Click to expand...
Click to collapse
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
sstar said:
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
Click to expand...
Click to collapse
I already did it twice
Now I finally got it working. I just charged it in Recovery Mode for a long time. Then I just used Webosdoctor and now it works!
Sent from my ss_tenderloin using xda app-developers app
help was trying to install ubuntu 13.04 on my touchpad end. and suddenly gave me an error and did not work well webos. turn it off. and try to rescue her with the webosdoctor 3.05 and finish everything well. but now the only tablet on and displays the HP icon and then restarts and so on
I hope you can help me fix it.
lildark7 said:
help was trying to install ubuntu 13.04 on my touchpad end. and suddenly gave me an error and did not work well webos. turn it off. and try to rescue her with the webosdoctor 3.05 and finish everything well. but now the only tablet on and displays the HP icon and then restarts and so on
I hope you can help me fix it.
Click to expand...
Click to collapse
Read this : http://forum.xda-developers.com/showthread.php?t=1426244
You might have to go this route. Read the whole thing, there's a lot of good information there. If you're having trouble with novaterm, there's a work around on page 12.
Good luck.
help
chicle_11 said:
Read this : http://forum.xda-developers.com/showthread.php?t=1426244
You might have to go this route. Read the whole thing, there's a lot of good information there. If you're having trouble with novaterm, there's a work around on page 12.
Good luck.
Click to expand...
Click to collapse
thanks but the problem is that the partitions are damaged. I always start the Webos is loading the HP logo and then restarts. reappears the HP logo and then restarts and so on
lildark7 said:
thanks but the problem is that the partitions are damaged. I always start the Webos is loading the HP logo and then restarts. reappears the HP logo and then restarts and so on
Click to expand...
Click to collapse
Right. That's what this guide walks you through. Basically, you're resetting the partitions to their original setting. That's why you need doctor 3.0.0, it's the only one that can handle these partitions. You can then upgrade to 3.0.5, install android, whatever.
Read the whole thing and make sure that the battery is completely charged. You don't want to run out of power in the middle of the procedure.
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
spica123 said:
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
Click to expand...
Click to collapse
EDIT: Okay. at least acmeuninstaller brought webos back to life.
OK so I'm just going to explain everything I did and ask how we can fix this. I was following the guide to install LuneOS and I got lost somehow and could not put the new boot image and new moboot image on after I removed the old boot image, so I tried to reboot (I know that was dumb) but then I got a error message about no Palm ROM. So I booted into the only thing I could boot into WebOS Recovery. Now I figured I would try out jcsullins Touchpad Toolbox I was able to load it and I figured the only way I could make it work would be to remove and reinstall WebOS to get the boot image back, so I wiped the touchpad (again probably not the best thing to have done). I then went to go and reinstall WebOS and the WebOSdoctor(webosdoctor305) I used failed after 8%(should I try a different doctor?). I then tried to install Android with Toolbox and it failed after checking the files(not sure if that was just bad files or issue with touchpad). I can still access WebOS recovery and use novaterm by finding the batch file on my computer and running it and I can still use Toolbox. Any help would be greatly appreciated and if you have any questions of what steps I took I will be happy to answer if it can help my touchpad.
spenser715 said:
OK so I'm just going to explain everything I did and ask how we can fix this. I was following the guide to install LuneOS and I got lost somehow and could not put the new boot image and new moboot image on after I removed the old boot image, so I tried to reboot (I know that was dumb) but then I got a error message about no Palm ROM. So I booted into the only thing I could boot into WebOS Recovery. Now I figured I would try out jcsullins Touchpad Toolbox I was able to load it and I figured the only way I could make it work would be to remove and reinstall WebOS to get the boot image back, so I wiped the touchpad (again probably not the best thing to have done). I then went to go and reinstall WebOS and the WebOSdoctor(webosdoctor305) I used failed after 8%(should I try a different doctor?). I then tried to install Android with Toolbox and it failed after checking the files(not sure if that was just bad files or issue with touchpad). I can still access WebOS recovery and use novaterm by finding the batch file on my computer and running it and I can still use Toolbox. Any help would be greatly appreciated and if you have any questions of what steps I took I will be happy to answer if it can help my touchpad.
Click to expand...
Click to collapse
Wear exactly do you what with your tp webos or android or both? You could have saved yourself and just put moboot back on lol