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.

[Q] System files and SD are stuck in read only mode

Hey Guys
So I thought I found a great deal on craigs list... touch pad for a good price... but it turns out I bought more then I barganed for. To cut to the chase the old owner seems to have a semi installed CM9 installed, but the something messed up and now im the new owner... :crying:
I tried to delete this guys photos in WebOS but he keeps coming back to huant me! IT seems that all the files are locked in read only mode and factory restores wont work
I tried this post
[Guide] Factory condition restoration / Downgrade to webOS 3.0.0
http://forum.xda-developers.com/showthread.php?t=1426244
and
[HOWTO][CM7 ALPHA2.1] FIX - sdcard storage mounts as readonly
http://forum.xda-developers.com/showthread.php?t=1322127
so far with no luck..
When i Tried Doctor os it fails at %12
Any suggestions guys?
PLEASE HELP

I once royally screwed mine by using windows to format it. You could try that...
WebOS doctor and the novaterm will get it going after that...
Just an idea...
Sent from my SAMSUNG-SGH-T989 using xda premium

I tried both WebOS = Failed at 12%
Novaterm =factory reseting and some other stuff
Please help :crying:
-SGA- said:
I once royally screwed mine by using windows to format it. You could try that...
WebOS doctor and the novaterm will get it going after that...
Just an idea...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse

Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium

I'm able to mount and format but when I reboot that guys photo is back Along with the system files and folders
QUOTE=-SGA-;33722106]Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium[/QUOTE]

Update
So I was able to boot into clock work with this thread :
http://forum.xda-developers.com/showthread.php?t=1302433
Comman used : novacom boot mem:// < uImage.ClockworkMod
Once in there I tried all the various options
format sd card / fix permissions / wipe X options
I also tried : CM7: Fixes for SDCARD issues
from : http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/page__st__90
but when i load files into the sdcard via mounting through clockwork Im unable to install from zip from SD card... due to the read only nature of this current drive...
My new Lead on this problem is from this thread : http://newbrightidea.com/2011/08/26/hacking-the-touchpad-part-1/
what caught my eye was his statement about mounted read only by default... (see below)
in theory if i follow his steps i may be able to unlock this read only bug and fully install CM9... Stay tuned.
STARTING OPENSSH SERVER
Harder than it sounds! The root filesystem is mounted read-only by default, but you can hack your way around that with:
mount -w -o remount /
Then, add the sshd user and group to /etc/passwd and /etc/group
Setup an ssh key using ssh-keygen and set the “HostKey” property in sshd_config to point to the private key.
If you didn’t remount the root FS as read-write, you need to set UsePrivilegeSeparation to true.
Start sshd like so:
krunktor said:
I'm able to mount and format but when I reboot that guys photo is back Along with the system files and folders
QUOTE=-SGA-;33722106]Did you try mounting the SD in windows through webos and then right clicking on the drive and click format?
Sent from my aokp_tenderloin using xda premium
Click to expand...
Click to collapse
[/QUOTE]

Removed.

emuX said:
Removed.
Click to expand...
Click to collapse
EmuX
are you refering to this post:
http://forum.xda-developers.com/showpost.php?p=24047078&postcount=3

Yes, I was. That's why I removed the post since you'd already found it. Although I didn't do all the steps suggested - just the first few and then ran webos doctor with it all uninitialised.
I just did:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Click to expand...
Click to collapse
(Oh, and I've got a 32gb device in case that makes any difference.)
Also, how long did you wait for webos doctor to complete? After using that approach I left mine running for a long time at 8% or 12% (I forget which) and it eventually carried on.

Clean Install (webos doctor disconnect at 4%)

Hey there
I'd like to sell my Touchpad, and wanted to get it clean and updated for the new user
Few weeks ago I updated to CM 10.2 and used tailor
system - 600mb
cache - 200mb
media - 400mb
data - 26gb
Now I booted into webos, wanted to upgrade the catalog app and others, changed date to Jan 2013,but it seems no memory left, now if I press install catalog, or the update, the TP reboots. Under device I see 0.3Gb available
How do I give Webos more space ? Is it the media partition ? Or not at all ? I'll try to resize it but tailor is having trouble to start
Also what are the Resets Options I can use after all is updated ?
Erase USB drive ? Or should I go first with full erase ? (apps install and data+usb drives etc) then update ?
Won't it mess with android install ?
Thanks for help !
Edit : Tailor : after a while, I get Service Error (userId) org.webosinternals.tailor.nod is not running, hmm, any idea to fix this ?
Reinstalled, retrying
I ran ACMEUninstaller, and tried webos doctor, 3.0.5, 3.0.4, 3.0.0, but everytime, it gets disconnected at 4%, using original cable, also tried with samsung's one
Any idea ?
Edit : I deleted media partition from tailor, then remade it, but it said fail, then I did an ext3 one, and the media appeared, but it said system was corrupted and I should try to repair, tried several time, no success, so I plug the tablet, and windows asked to format the partition, not sure If I chose ntfs or fat32, the default one, don't know if webos needs a specific one to work.
Rebooting the tablet now, taking some time but it's reinstalling some apps I think.
I'll retry doctor after that, if partition is here and not broken as before it may work, I hope => It doesn't.
Soo, I did full reset from webos, dunno if that's me or hp, but took me 10m to log in my account... Now restoring some stuff, but it often looses connectivity to hp. Hell !

Ps2004 said:
Hey there
I'd like to sell my Touchpad, and wanted to get it clean and updated for the new user
Few weeks ago I updated to CM 10.2 and used tailor
system - 600mb
cache - 200mb
media - 400mb
data - 26gb
Now I booted into webos, wanted to upgrade the catalog app and others, changed date to Jan 2013,but it seems no memory left, now if I press install catalog, or the update, the TP reboots. Under device I see 0.3Gb available
How do I give Webos more space ? Is it the media partition ? Or not at all ? I'll try to resize it but tailor is having trouble to start
Also what are the Resets Options I can use after all is updated ?
Erase USB drive ? Or should I go first with full erase ? (apps install and data+usb drives etc) then update ?
Won't it mess with android install ?
Thanks for help !
Edit : Tailor : after a while, I get Service Error (userId) org.webosinternals.tailor.nod is not running, hmm, any idea to fix this ?
Reinstalled, retrying
Click to expand...
Click to collapse
your media partition is way too small for webos. You need at least 1 GB. I would leave it at 5GB unless you aren't planning on using webos at all.
You have to remove space from data. In Tailor you need to unmount, check, and then resize.
To clean your CM 10.2 you should be able to just clear data from CWM.

Thanks for your reply, seeing you're pretty new, it's really nice
I tried resizing to 2GB, it didn't really work, I mean tailor says partition size is 2GB, then filesystem size is 399MB, webos only finds 399, same when connected to pc, and If I try resizing it says operation failed!
Or Could I try delete that partition without breaking the webos ? Then create it again 2GB from start, not sure tailor would manage but maybe ??
Otherwise, someone told me to use ACMEUninstall, and then run webosdoctor ? Is it really safe ? (I heard about people freezing with that app in past, so I'd like to avoid bad things)
Edit : as Tailor wouldn't manage to resize I followed what someone else told me, but think that was a bad idea, not sure yet, ran ACMEUninstall, then it booted on webos, no pb, I retried to use tailor no success, so I ran webos doctor, but it lost connection after 4%... Now looking about what to do, gonna retry this...
Found this, but doesn't seem to be for the touchpad, and the code gives me nothing so, dunno what to do now

Ps2004 said:
Thanks for your reply, seeing you're pretty new, it's really nice
I tried resizing to 2GB, it didn't really work, I mean tailor says partition size is 2GB, then filesystem size is 399MB, webos only finds 399, same when connected to pc, and If I try resizing it says operation failed!
Or Could I try delete that partition without breaking the webos ? Then create it again 2GB from start, not sure tailor would manage but maybe ??
Otherwise, someone told me to use ACMEUninstall, and then run webosdoctor ? Is it really safe ? (I heard about people freezing with that app in past, so I'd like to avoid bad things)
Edit : as Tailor wouldn't manage to resize I followed what someone else told me, but think that was a bad idea, not sure yet, ran ACMEUninstall, then it booted on webos, no pb, I retried to use tailor no success, so I ran webos doctor, but it lost connection after 4%... Now looking about what to do, gonna retry this...
Found this, but doesn't seem to be for the touchpad, and the code gives me nothing so, dunno what to do now
Click to expand...
Click to collapse
[Guide] Factory condition restoration
http://forum.xda-developers.com/showthread.php?t=1426244
gives this a shot

Alright thanks I'll try this
Seems easy, if all goes well
Running webosdoctor 3.0.0 now, 18% and going, sweet , after it I'll run 3.0.5, fix the store, and all should be fine, then clean cm10.x install
But, got a little question before I'm done, can you switch webos user account, email, without reseting the TP ? (and loosing the store fix ?)
Or should I be ok just getting a new pw, for it before selling, and tell the new buyer to change email and other infos on webos site ?

[Q] Accidently ran WebOS update and fubared everything

Any idea on how to fix this? A basic explanation would appreciated.
I came across this thread: http://forum.xda-developers.com/showthread.php?t=1564938
But I'm having some trouble following it

A little more info would be helpful....
Did you have android installed? Which version?
Webos update from within webos or using webos doctor, or...? What were you doing before the touchpad became fubar?
What do you mean by fubared? What can you / can't you do?
Does the device actually boot? If not, where does it hang?
Cheers

Sorry for the lack of detail.
chris5s said:
A little more info would be helpful....
Did you have android installed?
Click to expand...
Click to collapse
Yes I did, dual booted with WebOS.
chris5s said:
Which version?
Click to expand...
Click to collapse
I don't remember the exact one. I believe it was a CM9 nightly. It's not any of the new ones...and it was running one of the original recoveries as well.
chris5s said:
Webos update from within webos or using webos doctor, or...?
Click to expand...
Click to collapse
Within WebOS.
chris5s said:
What were you doing before the touchpad became fubar?
Click to expand...
Click to collapse
I booted into WebOS to check it out and it prompted me saying it needed to update. So I went ahead and let it do that.
chris5s said:
What do you mean by fubared?
Click to expand...
Click to collapse
It turns on to the HP logo, the logo acts like it's loading. Then it turns off, restarts, goes back to the HP logo, then continues this dance until the battery dies. When the battery dies the red battery picture shows up until it fully charges again.
chris5s said:
What can you / can't you do?
Click to expand...
Click to collapse
I can't get into the recovery, and I can't get into Android or WebOS. I can force restart it.
chris5s said:
Does the device actually boot? If not, where does it hang?
Click to expand...
Click to collapse
It hangs at the HP logo.
chris5s said:
Cheers
Click to expand...
Click to collapse
Thanks for any help!

I'm wondering, did webos perform a system upgrade, i.e. from version 3.0.x to 3.0.y, and in doing so it has screwed up your system partitions?
Did the touchpad reboot itself after 'upgrading'? If so, it probably was the above.
There may be a way to boot into webos recovery and repair the partitions, I'm not sure. Unless there's stuff on your touchpad that you want to keep (on the android partitions), I would be tempted to boot into webos recovery (holding volume up while pressing power), use AcmeUninstaller2, and then try booting into webos. If it won't boot, reboot into webos recovery and use webos doctor to rebuild webos system and then reinstall android.
Not an ideal solution, I know, as you will lose stuff on the tablet. Like I said, there may be a way of putting it into recovery and using novaterm to rebuild without a full uninstall/install.
Hope this helps!
Cheers

scl23enn4m3 said:
Any idea on how to fix this? A basic explanation would appreciated.
I came across this thread: http://forum.xda-developers.com/showthread.php?t=1564938
But I'm having some trouble following it
Click to expand...
Click to collapse
chris5s said:
I'm wondering, did webos perform a system upgrade, i.e. from version 3.0.x to 3.0.y, and in doing so it has screwed up your system partitions?
Did the touchpad reboot itself after 'upgrading'? If so, it probably was the above.
There may be a way to boot into webos recovery and repair the partitions, I'm not sure. Unless there's stuff on your touchpad that you want to keep (on the android partitions), I would be tempted to boot into webos recovery (holding volume up while pressing power), use AcmeUninstaller2, and then try booting into webos. If it won't boot, reboot into webos recovery and use webos doctor to rebuild webos system and then reinstall android.
Not an ideal solution, I know, as you will lose stuff on the tablet. Like I said, there may be a way of putting it into recovery and using novaterm to rebuild without a full uninstall/install.
Hope this helps!
Cheers
Click to expand...
Click to collapse
Yep sounds like you need to run the ACMEUninstaller2 and then the WebOS doctor to fix your tablet, this should help
How and when to Use the WebOS Doctor(Important):
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Important): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.0 to 3.0.5 Official Links
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode. Note the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.

chris5s said:
Hope this helps!
Cheers
Click to expand...
Click to collapse
RolandDeschain79 said:
Yep sounds like you need to run the ACMEUninstaller2 and then the WebOS doctor to fix your tablet, this should help
Click to expand...
Click to collapse
You both are absolutely awesome people! Worked perfectly and took much less effort than I was expecting to put in. Thank you!

Also, is WebOS doctor required if it booted into WebOS after the acmeuninstaller?

I would say not, if webos is working as it should, sounds like all is good.
However using the doctor - 3.0.0 then updating to 3.0.5 - might not be a bad idea, just so all your 'housework' is up to date and the tablet is back to original condition. Try using webos a bit and see, it may not be necessary...
Cheers

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