Database Develop

[Q] Unable to reset Touchpad, even with webosdoctor

I am just about to give up any software solution and contact HP to see if they can fix this as a hardware problem.
But before I do that, i thought it might be worthwhile to post my problem here first.
My touchpad has been running fine, and operating without any problems until recently when I installed new apps or downloaded new files on the touchpad.
While the touchpad was up and running, everything was fine, the apps appeared in the menu, and the files copied could be accessed without any problems.
In terms of functionality there was nothing to suggest any problems with the TP.
However, whenever I reboot the TP (soft or hard reboot), all newly installed apps or files disappear and the TP reverts back to a previous state. Nothing that I do to the TP remains after a reboot.
So I downloaded the latest webosdoctor 3.0.5 to reset the TP but after getting to about the dreaded 12% mark, the webosdoctor fails, spewing out a lot of message about parted failure and something about the flash.
Following all the tips on using novacom to boot the uImage and accessing the TP from novaterm does not seem to work as any fix initiated is lost on the following reboot.
Even while logged in to the TP via novaterm, and using lvm.static to remove the logical and physical volume to see if I can get webosdoctor to recreate the partitions did not work.
The command lvm.static vgremove reported to successfully remove the logical drive, but on subsequent scan using lvm.static vgscan shows that the logical drive is still persistent.
Removing physical volume using lvm.static pvremove did not work.
In frustration I deleted /dev/mmcblk0p14 (and all the mmcblk0???). Consequently the lvm.static scans showed no logical drive available.... but on subsequent reboot they are all back.
Webosdoctor again failed with same problem when rebooted.
It seems like the TP is falling back to some default memory (partition) state and nothing that I do remains persistent. I can't see anyway I can force the partition tables to reset as any changes are lost on reboot.
So unless someone can suggest something different, I am resigned to having to call HP and send my TP in for repairs.
Does anyone else have similar experience?
P.S. this started after I updated to webOS 3.0.5 but I can't say this was the exact cause.

I have the same problem with my touchpad. Are there any solutions?

it looks like the only way to get it fixed is to contact HP and send your TP back for repairs.
I will be contacting them next week when I have time to organise for it to be repaired.

Have you tried to run the WebOS 3.0.0 Doctor? It will resize all of the partitions and leave you with a fresh copy of WebOS. It can be found here: "http://www.webos-internals.org/wiki/Webos_Doctor_Versions".
Here is what I did:
1.Completely shut down
2.Boot into recovery menu by holding Volume-Up button and then pressing the power button.
3.Run WebOS 3.0.0 doctor
If it halts for any reason, let me know what percentage it stopped on, and perhaps I can help you out.

As I have tried to outline in the OP, I have tried webosdoctoring from version 3.0.0 to 3.0.5
It doesn't have any effect as any changes to the partition is lost once the TP reboots.
I know webosdoctor 3.0.0 is the standard answer for all partition related problems, but I think in my case it is not a partition problem but more of the flash controller, that is hardware related. It might have gotten itself into a funny state where it is constantly going into fall back mode after every reboot.

I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.

colin_404 said:
I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.
Click to expand...
Click to collapse
This did not work for me. There is no way to remove /store

I'm having the same problem.
Device:
HP Touchpad 32 GB
WebOS: 3.0.4
Android: CM9 A2
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
What works:
- It loops while booting to Android
- It boots to Clockwork Recovery
- It boots to WebOS Recovery
- It boots to WebOS
- Everything works inside WebOS
- I can connect through Novaterm
What I've tried so far with no success:
- Recreating the file system
- Formating the internal storage
- Running a checkdisk
- Partitioning the storage
- Reinstalling Android
- Running WebOS Doctor 3.0.0, 3.0.4, 3.0.5

narci2500 said:
I'm having the same problem.
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
Click to expand...
Click to collapse
Nothing worked for me. Tried every trick suggested, even mixed things a bit. In the end I had to send it back to HP for it to be fixed.
All good now, it came back all fixed.

I'm having the same issue. Did they accept the return even with Android on it?

djteiwaz said:
I'm having the same issue. Did they accept the return even with Android on it?
Click to expand...
Click to collapse
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.

cychoi75 said:
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.
Click to expand...
Click to collapse
good to know, thanks

So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?

djteiwaz said:
So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?
Click to expand...
Click to collapse
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?

rr5678 said:
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?
Click to expand...
Click to collapse
Not yet. Should have it back by this weekend.

I also have this problem and have tried restoring my touchpad with numerous fixes on this site but they all fail and the touchpad just reboots to its previous state.
any help would be appreciated

Received it back. Would love some recommendations for possible fixes.

djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Okay. I'll gather some information now.

djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.

rr5678 said:
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.
Click to expand...
Click to collapse
Not a problem. I appreciate you spending time on this for me.

[A] How to Install Android without setting up webOS

Solved - Follow this - http://forums.webosnation.com/hp-touchpad/318426-how-install-android-without-setting-up-webos.html
Here is a series of steps that lead me to this problem.
1) I wanted to give my touchpad to a friend of mine. So I removed the dual boot. I also booted to WebOs and did a factory reset. The touch-pad is now in pristine state. So far so good. No problems.
2) My friend takes the touchpad from me but never goes thru the setup. He then looses it !!
3) Once I came to know about it, I went online and initiated a remote wipe. I don't know why I did that since it was already clean (from step 1 above). I think this action of mine created a problem.
4) My friend finds the Touchpad. It was in his home all along. So I charged it and then boot into WebOs.
5) This is where the problem starts. The initial webOs setup requires that I set up a new account with HP ( or use an existing one). First, I tried to use my existing account (the same that I used in step 3). It won't log in saying that there is a login error, try again or contact HP support. The password is correct, since I am using the same password on the HP website and I can see my device there.
6) I then tried to create a new account using a different email. To my surprise, that failed too. I tried a few other emails, all with same results. The new account creation was failing in all these cases.
7) Now I am stuck. I have emailed HP for support but I was hoping someone else had any other ideas. I am out of warranty. So email support is the only thing that I can get from HP.
8) Is there is a way I can install Android on it without launching webOs - Can I create a cmInstall folder from WebOs recovery ? ANy Novacom driver option to access the file system ? The only way to get the cminstall folder (that I know of) is to boot into webOs and I cannot do that.
I have tried a few other things that came to my mind.
1) I used WebOs Doctor to do a clean install. It still did not help. The log-in still fails.
2) I removed the device from my old account thinking that it might be the reason my new account creation is failing. But that did not help.
Any suggestion or links that might help me would be really appreciated.

[email protected] said:
Here is a series of steps that lead me to this problem.
1) I wanted to give my touchpad to a friend of mine. So I removed the dual boot. I also booted to WebOs and did a factory reset. The touch-pad is now in pristine state. So far so good. No problems.
2) My friend takes the touchpad from me but never goes thru the setup. He then looses it !!
3) Once I came to know about it, I went online and initiated a remote wipe. I don't know why I did that since it was already clean (from step 1 above). I think this action of mine created a problem.
4) My friend finds the Touchpad. It was in his home all along. So I charged it and then boot into WebOs.
5) This is where the problem starts. The initial webOs setup requires that I set up a new account with HP ( or use an existing one). First, I tried to use my existing account (the same that I used in step 3). It won't log in saying that there is a login error, try again or contact HP support. The password is correct, since I am using the same password on the HP website and I can see my device there.
6) I then tried to create a new account using a different email. To my surprise, that failed too. I tried a few other emails, all with same results. The new account creation was failing in all these cases.
7) Now I am stuck. I have emailed HP for support but I was hoping someone else had any other ideas. I am out of warranty. So email support is the only thing that I can get from HP.
8) Is there is a way I can install Android on it without launching webOs - Can I create a cmInstall folder from WebOs recovery ? ANy Novacom driver option to access the file system ? The only way to get the cminstall folder (that I know of) is to boot into webOs and I cannot do that.
I have tried a few other things that came to my mind.
1) I used WebOs Doctor to do a clean install. It still did not help. The log-in still fails.
2) I removed the device from my old account thinking that it might be the reason my new account creation is failing. But that did not help.
Any suggestion or links that might help me would be really appreciated.
Click to expand...
Click to collapse
When you tried to doctor, did you go back to 3.0.0? If you didn't, here's a good guide :
http://forum.xda-developers.com/showthread.php?t=1426244
You have to go back to 3.0.0 because it's the only one who can handle partitions. After you successfully do 3.0.0, you can update to 3.0.5 OTA. Then install android the usual way.
Read the whole thing. Around page 12 there's a good work around if you're having trouble with novaterm.
Good luck.

chicle_11 said:
When you tried to doctor, did you go back to 3.0.0? If you didn't, here's a good guide :
http://forum.xda-developers.com/showthread.php?t=1426244
You have to go back to 3.0.0 because it's the only one who can handle partitions. After you successfully do 3.0.0, you can update to 3.0.5 OTA. Then install android the usual way.
Read the whole thing. Around page 12 there's a good work around if you're having trouble with novaterm.
Good luck.
Click to expand...
Click to collapse
Yes I did doctor to 3.0.0. The problem is not that I am unable to install WebOs. The problem is that when the setup screen comes and I provide the user-id/password, it doesn't take it. It seems like my Serial Number is somehow blocked by HP since I did a remote erase. Or maybe the remote erase and the initial setup are getting deadlocked - neither the remote erase can complete since its waiting for login to happen - and the login cannot complete since it thinks erase is in progress.

[email protected] said:
Yes I did doctor to 3.0.0. The problem is not that I am unable to install WebOs. The problem is that when the setup screen comes and I provide the user-id/password, it doesn't take it. It seems like my Serial Number is somehow blocked by HP since I did a remote erase. Or maybe the remote erase and the initial setup are getting deadlocked - neither the remote erase can complete since its waiting for login to happen - and the login cannot complete since it thinks erase is in progress.
Click to expand...
Click to collapse
Then I think only HP support can help. They have to unblock your serial number / account so you can have access.

chicle_11 said:
Then I think only HP support can help. They have to unblock your serial number / account so you can have access.
Click to expand...
Click to collapse
But I was hoping that even though I cannot log in, I can at least install Android. But to do that, I need to be able to create a cminstall folder and I cannot do that unless I can see the touch-pad file system from my PC. I was hoping that there is a way to do that without logging into WebOs. Meanwhile I am still waiting for HP to respond back to my email !!

Possible solution to this problem - bypass activation
http://forums.webosnation.com/hp-to...ources/317164-activation-bypass-touchpad.html
I haven't tried it but this gives me hope. I might be able to bypass activation after all !!

How to Install Android without setting up webOS
Seems like someone had the exact same problem that I had. Thanks Google.
http://forums.webosnation.com/hp-touchpad/318426-how-install-android-without-setting-up-webos.html

Touchpad stuck in a read only mode

I have a TP with WebOS 3.0.5, Moboot 0.3.8, and CM10.1.
Whenever I reboot my device, any changes I make are reset. I can't load a new ROM. I can copy files to my SD Card and use them, but when I reboot, the files are gone. I see this is an ongoing issue. But most threads are old. Any fix for this? I just want to be able to run WebOS doctor now, but it won't work. It stops at 12% and says Unable to Reset. I have tried all the various WebOS doctor versions from 3.0.0 to 3.0.5.
Thanks,

asif9t9 said:
I have a TP with WebOS 3.0.5, Moboot 0.3.8, and CM10.1.
Whenever I reboot my device, any changes I make are reset. I can't load a new ROM. I can copy files to my SD Card and use them, but when I reboot, the files are gone. I see this is an ongoing issue. But most threads are old. Any fix for this? I just want to be able to run WebOS doctor now, but it won't work. It stops at 12% and says Unable to Reset. I have tried all the various WebOS doctor versions from 3.0.0 to 3.0.5.
Thanks,
Click to expand...
Click to collapse
Use jcsullins hp TouchPad Toolbox. Complete reset.

Moody66 said:
Use jcsullins hp TouchPad Toolbox. Complete reset.
Click to expand...
Click to collapse
Cool thanks. This looks like it could be the thing. Do you recommend I do a Full Data Reset to delete both WebOS and Android, then Create WebOS Volume to prep the device for WebOS, then WebOS doctor to get back to factory? Then if all goes well, then re-install Android?
I ask because the Full Data Reset sounds scary. I hope I can still access Moboot from there, for whatever that's worth.

Moody66 said:
Use jcsullins hp TouchPad Toolbox. Complete reset.
Click to expand...
Click to collapse
I posted in the Toobox thread, but just fyi, can you believe, Complete Reset didn't work! It's like my Touchpad is in read only mode.

asif9t9 said:
I posted in the Toobox thread, but just fyi, can you believe, Complete Reset didn't work! It's like my Touchpad is in read only mode.
Click to expand...
Click to collapse
Same exact thing is happening to me. Toolbox message says:
Code:
ERROR: LVM config erase check FAILED. Possible read-only failure.
I have tried everything, and when it reboots, it is as if nothing changed. Check this out:
Code:
[email protected]:/# lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
11 logical volume(s) in volume group "store" now active
[email protected]:/#
[email protected]:/# lvm.static vgremove store
lvm.static vgremove store
Do you really want to remove volume group "store" containing 11 logical volumes?
[y/n]: y
y
Do you really want to remove volu......
It says it's removed:
Code:
Logical volume "cm-data" successfully removed
Volume group "store" successfully removed
Then right after:
Code:
lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
Found volume group "store" using metadata type lvm2
STILL THERE!! LOL this is crazy... is it a hardware problem?
NOTE: This touchpad was sitting dead for 6 months. Charged it, turned it on, read only ..

I'm sad but glad at the same time others are afflicted the same as me. It means others are trying to fix problem so we might get a solution. I have this beautiful touchpad sitting at home dead now. When it did work, it was in read only mode. But the battery died out again and now I can't get it started up at all. But I know the battery itself is fine because when it was working...in read only mode...the battery held charge really well.

asif9t9 said:
I'm sad but glad at the same time others are afflicted the same as me. It means others are trying to fix problem so we might get a solution. I have this beautiful touchpad sitting at home dead now. When it did work, it was in read only mode. But the battery died out again and now I can't get it started up at all. But I know the battery itself is fine because when it was working...in read only mode...the battery held charge really well.
Click to expand...
Click to collapse
I used a *touchstone to charge mine. I've heard that can make a difference.
There are few threads on this read-only issue, but no fixes...

camaroqqq said:
I used a touchpad to charge mine. I've heard that can make a difference.
There are few threads on this read-only issue, but no fixes...
Click to expand...
Click to collapse
Yeah the Touchstone worked the last time for me to charge it up. But it's not working anymore. Hard to believe two charging methods have failed at the same time. Either way I need to melt down the device to dispose of it because it has personal info and photos on it.

Getting same issues, been trying to sort for ages
This is what the state of mine is
Boots up Moboot 0.3.5
Cyanogenmod does not load just loops
Does boot WebOS but Cannot Wipe the device, it reboots and nothing has changed, even removed a app and reboot and comes back again.
tried toolbox complete wipe says read only mode
WebOS Doctor recovery dies at 12%
tried the Guide to recover and everytime I rescan, it finds the "store" yet again, even after I've deleted it.
now confused, I can charge it too 100% with no issues, but found it best not to charge it on USB recovery mode, seems to charge ok from complete shutdown or in webos.
but read only mode cant fix tried loads of stuff but seems every post with others with issues seems to go off on something else un-related from the issue.

Mine froze on Oct. 11
Yes, somewhat comforting to know that there are a few other cases of this. My first symptoms were that apps were starting to crash. Then I noticed that nothing I did would change the bootup state. Seems like a file system problem, but how could that information get overwritten at bootup? I hope one of the experts can shed some light on this problem.
earthcoder said:
Getting same issues, been trying to sort for ages
This is what the state of mine is
Boots up Moboot 0.3.5
Cyanogenmod does not load just loops
Does boot WebOS but Cannot Wipe the device, it reboots and nothing has changed, even removed a app and reboot and comes back again.
tried toolbox complete wipe says read only mode
WebOS Doctor recovery dies at 12%
tried the Guide to recover and everytime I rescan, it finds the "store" yet again, even after I've deleted it.
now confused, I can charge it too 100% with no issues, but found it best not to charge it on USB recovery mode, seems to charge ok from complete shutdown or in webos.
but read only mode cant fix tried loads of stuff but seems every post with others with issues seems to go off on something else un-related from the issue.
Click to expand...
Click to collapse

Well this sucks... I appear to be stuck with the same issue as everyone else in this thread.
I mounted media volume in toolbox and used windows for format the drive. When I mounted it again the data was all still there...

I'm sad to say I trashed mine. Couldn't fix it. And didn't want to sell for parts because the memory had my personal data. Still haven't replaced the tablet because I can't find a better model for the price.

anyone ?
Anyone was able to fix this ?
somehow it can't mount to /data , I've tried all commands related lvm.static ( vgremove , lvremove..... ) it shows removed but after restart still there and nothing has changed.
tptoolbox could not fix , could not remove partitions .
acmeuninstaller and acmeuninstaller2 could not remove .
is this hardware issue or software ?

What version of TPToolBox are you using?
I haven't yet run across this problem in numerous wipes on (7) TPs.
Had one that the Mobo had gone bad on - couldn't do anything on that one. Another had a video gremlin, but I was still able to wipe it.
I wonder if maybe ADB and using shell commands might work?
_Dan

TPToolbox issues

*UPDATE*
It looks like I managed to recover from this completely. I ended up doing a second TPDebrick but I made sure I specified 32gb this time. I don't recall what I put in last time but I'm guessing it wasn't 32 and that is what wrecked my partitions.
To preface, I had bricked my Touchpad and used TPdebrick to get it to boot again. I now have access to the boot menu and can get to TWRP and WebOS recovery just fine. However, TWRP won't let me install any .zips and shows 0mb on both the /system and the /data partitions. TPToolbox gives me a slew of problems such as :
Install Android or Resize Android Volumes
- Problem w/ vgchange -ay
Repair Android Volumes
- FAILED: rc=5: vgchange -ay
Complete Data Reset
- ERROR: Invalid partition info: end-gap greater than 1 percent of mmc
I'm using the same TPToolbox v42 that I used to originally install Android on my Touchpad. Just to confirm the files hadn't corrupted somehow I redownloaded the toolbox and tried again to the same results. Any help would be appreciated. I'm pretty good with basic/intermediate Android stuff but I feel a little over my head with this stuff.
*edit* I have since tried WebOS Doctor and it has told me it cannot fix my device either.

CriticalComposer said:
*UPDATE*
It looks like I managed to recover from this completely. I ended up doing a second TPDebrick but I made sure I specified 32gb this time. I don't recall what I put in last time but I'm guessing it wasn't 32 and that is what wrecked my partitions.
To preface, I had bricked my Touchpad and used TPdebrick to get it to boot again. I now have access to the boot menu and can get to TWRP and WebOS recovery just fine. However, TWRP won't let me install any .zips and shows 0mb on both the /system and the /data partitions. TPToolbox gives me a slew of problems such as :
Install Android or Resize Android Volumes
- Problem w/ vgchange -ay
Repair Android Volumes
- FAILED: rc=5: vgchange -ay
Complete Data Reset
- ERROR: Invalid partition info: end-gap greater than 1 percent of mmc
I'm using the same TPToolbox v42 that I used to originally install Android on my Touchpad. Just to confirm the files hadn't corrupted somehow I redownloaded the toolbox and tried again to the same results. Any help would be appreciated. I'm pretty good with basic/intermediate Android stuff but I feel a little over my head with this stuff.
*edit* I have since tried WebOS Doctor and it has told me it cannot fix my device either.
Click to expand...
Click to collapse
So glad you posted this. This is exactly what I did. When your mind is in all this other stuff thats going on its easy to forget that it could be as simple as this. Thanks!

I've got the exactly same problem.
Had Evervolve Kitkat on my TP and I didn't charge it for a long period. After that I wasn't able to charge or wake it up again.
With TPDebrick I could end in the boot menu, bu any further TPToolbox action failed.
For me it seems, the necessary volumes are either not available or of size zero.
I would like to revive the beloved TP, but have no glue how to overcome this situation
@@@ SOLVED @@@
recreated volumes with this instructions
WebOSdoctor 3.0.0 loading ... TPToolbox next

Looking for a little help

Recently I started having issues with my touchpad, so I figured I would factory reset and install the latest whatever. Well I tried factory reset from the webos side and nothing changed, so I then tried from the CM9 side and still nothing. I tried WebOS doctor and it always locks at 12%. Then I tried TPtoolbox from the terminal and a complete date reset and it gave me an error "ERROR: LVM config erase check FAILED. Possible read-only failure" I then tried toolbox's repair android volumes and got "e2fsck: unable to set superblock flags on /dev/store/cm-cache" "Failed to correct errors on volume cm-cache".
I am worse than a complete newb when it comes to unix and could really use some help here. I was even so desperate that I was thinking of trying TPdebrick 0.4, but apparently unix hates my nvidia card, so even running that might be beyond me. So if anyone has a fix for this, I am dying to hear it. The errors on my cm9 are annoying as hell, I can barely run it enough to use it as an ebook reader atm. And with the popups that continually happen, it's very distracting.

I'm having the exact same issue since 2 days ago. my Touchpad froze up and now it gets stuck at the android loading screen. When i run touchpad toolbox to erase everything I get:
ERROR: LVM config erase check FAILED. Possible read-only failure.
I can't find a solution for this anywhere.