Database Develop

[Q] Recovering Touchpad

Hi folks,
I was using Cyanogenmod 9 before the nightly releases and have installed ubuntu. Well, yesterday i tried to reset it to a factory condition to reinstall just cm9 nightly along with WebOS.
I used the WebOS Doctor 3.0.0, and after it the TouchPad won't boot anymore, just stuck on HP Logo reset loop. So i have tried again with WebOS Doctor 3.0.5 and got the same...
Also, i have tried to reinstall directly moboot and these things with ACMEInstaller, but it claims anything about lvm not found. Now, i just can't do anything to touchpad. I can enter on USB mode (Pwr + VolUP), and connect with novaterm, but i dont know what to do.
Anyone can try to help me? I'll post more details if you tell me how to catch these.

What you need to do is use the info from THIS THREAD to help you reset. It'll erase and recreate all of the partitions on the TP and allow you to flash 3.0.0 properly (then you can flash 3.0.5 and then install CM9 again).
I just did it last night (again). It's the best guide I've found, anywhere.

Hi,
I saw this and did this but i missed to flash the Recovery uImage before i created this thread, a bad mistaken.
Thanks for help.

Tablet Constantly Reboots

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?

[Q] Trouble updating to CM10 3/4

I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!

rg2 said:
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
Click to expand...
Click to collapse
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.

You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.

chicle_11 said:
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
Click to expand...
Click to collapse
Thanks for the advice. Going to have to do this I guess.
sstar said:
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
Click to expand...
Click to collapse
I used them both, although I generally use TWRP. I got rid of CWM and tried again to no avail. Thanks for the reply.

Running ACMEuninstall and reinstalling did nothing to fix the problem. Still have "damaged SD card" prompt upon boot, still have broken wallpaper functionality as well as crippled launcher functionality. Any ideas?

How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.

sstar said:
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
Click to expand...
Click to collapse
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!

reset webos
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.

rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2

johna2u said:
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
Click to expand...
Click to collapse
Thanks for the tip. Will have to try this.
sstar said:
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help

rg2 said:
Thanks for the tip. Will have to try this.
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
Click to expand...
Click to collapse
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3

sstar said:
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
Click to expand...
Click to collapse
Thank you for the suggestion! I will try this since I seem to be cursed using the JCSullins build :/

HP Touchpad Toolbox not working????

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.

[Q] HELP!!! Removed boot image HELP!!! Can't boot

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