Database Develop

[Q] Can't get my Touchpad to boot Android or WebOS, nor can I factory restore

Sorry if I should post this in the Dev thread. I've been through the forums, I've googled around, and none of the guides have helped solve this. I'll succinctly describe what I did and where I'm at.
I had CM9 (oat's LnT ROM) and WebOS dual booting just fine. Since LnT was discontinued, I decided I'd see if maybe another ROM would work better since I was having issues. I put AOKP on via CWM. Now, however, both Cyanogen and AOKP showed up in my boot menu with Cyanogen as the default. One time I forgot to change what the boot was, and it tried (and failed) booting cyanogen.
Since then, I can't boot anything. CWM can't mount anything, so I can't get to my nandroid backup, webOS won't boot. I'd honestly be happy with a pure factory reset and starting from scratch, but I can't get anywhere with webos doctor either. It fails at 8%:
Oct 11, 2012 12:20:23 PM com.palm.nova.installer.recoverytool.CardController runnerFinished
WARNING: flashing failed, move to failed card
A found a guide at wwwDOTsouldevteamDOTnet/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad/ that looked promising, but I can't find any volumes:
[email protected]:/# lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
[email protected]:/#
Any advice or help would be most welcome.

stace said:
Sorry if I should post this in the Dev thread. I've been through the forums, I've googled around, and none of the guides have helped solve this. I'll succinctly describe what I did and where I'm at.
I had CM9 (oat's LnT ROM) and WebOS dual booting just fine. Since LnT was discontinued, I decided I'd see if maybe another ROM would work better since I was having issues. I put AOKP on via CWM. Now, however, both Cyanogen and AOKP showed up in my boot menu with Cyanogen as the default. One time I forgot to change what the boot was, and it tried (and failed) booting cyanogen.
Since then, I can't boot anything. CWM can't mount anything, so I can't get to my nandroid backup, webOS won't boot. I'd honestly be happy with a pure factory reset and starting from scratch, but I can't get anywhere with webos doctor either. It fails at 8%:
Oct 11, 2012 12:20:23 PM com.palm.nova.installer.recoverytool.CardController runnerFinished
WARNING: flashing failed, move to failed card
A found a guide at wwwDOTsouldevteamDOTnet/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad/ that looked promising, but I can't find any volumes:
[email protected]:/# lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
[email protected]:/#
Any advice or help would be most welcome.
Click to expand...
Click to collapse
This could be of help, though it's not complete, it's a start in the right direction.
http://forum.xda-developers.com/showthread.php?t=1729179
Good luck.
Edit : Here's another link that could help : http://forum.xda-developers.com/showthread.php?t=1426244

chicle_11 said:
This could be of help, though it's not complete, it's a start in the right direction.
http://forum.xda-developers.com/showthread.php?t=1729179
Good luck.
Edit : Here's another link that could help : http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Thanks for those links. Alas, the process in the second link presumes that the first command "vgscan" will find and identify a "store" volume. But mine doesn't find any volumes. I'll see if that author has any helpful advice on how I can create the volume group.

this should be a real simple fix. obviously you still have moboot working correct? and you are still able to boot into clockworkmodrecovery CWM correct?
now im guessing by the "failed at 8% issue that youre likely on windows 7 64bit orr maybe even vista 64bit correct?
do you have the android-sdk installed on your computer and are you familiar with how to enable ./adb connections?
if yes then this should only take a few minutes to fix.

I have moboot, and can boot into CWM, but CWM complains about not being able to mount any dirs.
I get the 8% issue whether I use Windows 7 64 bit or Mac OS 10.7.
I'm sure I can muddle through adb connections. Do you have any tips for me to try? I can't successfully get the tablet to boot anything -- the closest is CWM which, as I say, can't mount anything.

Read only file system

My friends touchpad has the infamous read only file system. I have tried every forum post recommendation so far and nothing has worked. Webos loads but nothing can be changed and android will not boot. I got as far as removing the android partitions and resizing the webos partitions back to default using acmne uninstaller. After that it seems everything became complete read only. I luckly still have moboot and cw mod. I would like to just delete all partitions and volumes and start fresh. I tried the following commands :
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgremove store
but not matter what store is never actually removed even though it says its deleting it vgscan always sees it. I also tried wiping volume metadata no go. I tried fsck to repair file system tried the cm7 sd card fixer but since e: is gone because acmneuninstall happened to work before it went read only, it wont run. since its been so long I cant send it back to hp especially with hacks done to it. Were there any recent discoveries on repairing the read only issue, as long as its not hardware failure? thanks.

[Q] Tailor won't file check android partition

I am attempting to resize my 32gb tp so I can use the JB 4.3 rom from a 4.2.2 rom. Following Roland's guide on how to use Tailor, I file checked the media partition which concluded successfully and then created new space from the media partition but when I went to add it to my android partition (408 gb) to get to 500, it asked me to file check the android partition. When I attempted this, Tailor froze for about 1 minute maybe 2, then told me the partition maybe damaged and I needed to attempt a recovery, This option was offered in Tailor and I tried it. It sat there for about 2 hours with a circle icon spinning but nothing happening. Being worried I had screwed up my android partition, I exited webos and rebooted into android. Everything was working fine. I returned to webos and attempted the steps in Roland's guide again with the same result. It is now sitting in the recovery process which I will leave overnight but I doubt it will conclude successfully. Has anyone else experienced this using tailor? If so, how did you solve? Any help would be appreciated.

silgel said:
I am attempting to resize my 32gb tp so I can use the JB 4.3 rom from a 4.2.2 rom. Following Roland's guide on how to use Tailor, I file checked the media partition which concluded successfully and then created new space from the media partition but when I went to add it to my android partition (408 gb) to get to 500, it asked me to file check the android partition. When I attempted this, Tailor froze for about 1 minute maybe 2, then told me the partition maybe damaged and I needed to attempt a recovery, This option was offered in Tailor and I tried it. It sat there for about 2 hours with a circle icon spinning but nothing happening. Being worried I had screwed up my android partition, I exited webos and rebooted into android. Everything was working fine. I returned to webos and attempted the steps in Roland's guide again with the same result. It is now sitting in the recovery process which I will leave overnight but I doubt it will conclude successfully. Has anyone else experienced this using tailor? If so, how did you solve? Any help would be appreciated.
Click to expand...
Click to collapse
I have seen this mentioned in other posts and it can take a long time, hours, for the check to complete. You may also have to try several times before it is successful. I don't know why, I'm just reporting what I have read. Good luck

Impossible to install Android

Hello,
there was Android installed before. But because it didnt boot I uninstalled Android like in the guide(video).
When I now try to put something in cminstall folder or create new cminstall, there is this issue:
i can temporary(!) delete/create and everythings seems fine. But once i plug out Touchpad and plug in again, there are the same files like before.
When i try to install with ACME command i get at the end this error on the Pad:
Unable to create unique name
Unable to locate filesystem on device "/dev/store/media".
resizefat failed! Aborting! Please reboot
I have another issue with WebOS.
I can't use Preware. When starting Preware it loads some stuff first and then there is a message at the top left:
template load failed: main/main-scene.html
Thanks for your help!

Sounds like you need a webos doctor.

With WebOS Doctor it stops at 12% and says "We were unable to reset your phone. Please go to Palm Support for help."
When i reboot everything is like before.

GuelleX said:
With WebOS Doctor it stops at 12% and says "We were unable to reset your phone. Please go to Palm Support for help."
When i reboot everything is like before.
Click to expand...
Click to collapse
This should help
http://forum.xda-developers.com/showthread.php?t=1426244

It didn't help.
Same issue, it stops at 12%. But this time on pad, there is black chip on left AND hp logo in center after that. Before there was only one of it (don't remember which).
Also this command gives an "error": lvm.static vgcreate -s 8M store /dev/mmcblk0p14
The name is invalid or something (i can try it again and tell what it says exactly if necessary).

Any other suggestions?

Have you tried the touchpad toolbox tool that JC Sullins came out with recently? I used it the other day quickly and flawlessly. It can rebuild the volumes for Android and/or WebOS (yes, you can wipe WebOS from the touchpad). Give it a whirl.

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