Database Develop

[SOLVED] BRICKED and WebOS Doctor Won't Help...

Problem solved! Thanks guys!
I was triple booting WebOS, CM9, and Arch Linux and decided to wipe with WebOS Doctor and start over with just WebOS and CM9. I get bootloops at the HP splash screen and was initially able to Doctor all the way with no success. I removed the LVM from CM9 and Arch from novaterm and have had no luck with doctoring passed 8% and still get nothing but bootloops.
Followed the instructions on the 7th post down on this page http://forums.webosnation.com/hp-touchpad/310767-touchpad-bootloop-doctoring-fail.html
And this page http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery
I think I'm screwed... Any help would be GREATLY appreciated. Thanks in advance.

sounds like you need to do a FULL wipe with novaterm, hang on im grabbin the link
EDIT** **** me im having the hardest time finding it :/ its what i needed to do to install archlinux using your guide

You need to rebuild the partitions.
Just follow these instructions to the letter and you should be good.
HOWTO for anyone interested: Updated on 2011 12-13
Update: resolved 'major:minor pair unavailable'
Update: Works for 32GB HP Touchpad and 16GB HP Touchpad
Credits to:
webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
for the 32GB HP Touchpad filesystem creation example
[FIRST]
1) THIS PROCESS WILL COMPLETELY WIPE YOUR TOUCHPAD! WEBOS, CM7,
& ANYTHING ELSE YOU'VE INSTALLED!!
2) This process also assumes you can get functional terminal to your HP
Touchpad already via novaterm, novacom open TTY://, or with putty.
3) This process also assumes you know how to install CM7 already.
YOU WILL ALSO NEED:
webOS Doctor version 3.0.0
webOS Doctor version 3.0.4
from All HP WebOS Doctor Versions:
webos-internals.org/wiki/Webos_Doctor_Versions
[NOW START]
1) Put your HP Touchpad in webOS Recovery Mode:
a. Power off the HP Touchpad or reset it with [Power Button] + [Home]
b. Hold [Up Volume] + [Power Button] until you see a usb symbol on screen.
2) Start up taskmanager in Windows:
a. [CTRL]+[ALT]+[DEL] and select task manager
3) Run webOS Doctor and let it run to 8% then use taskmanager to end task
on webOS doctor.
4) Open up windows command prompt and type in: novacom open TTY://
5) Run the following commands [CASE SENSITIVE] type it exactly as shown
and make sure to get the numbers after --minor correct:
[Note: Don't bother customizing webOS partitions because in this process
webOS doctor will re-size them back to the following anyways.]
a. lvm.static vgscan --ignorelockingfailure
b. lvm.static vgchange -ay --ignorelockingfailure
c. lvm.static vgremove store
d. lvm.static vgscan --ignorelockingfailure
e. lvm.static vgchange -ay --ignorelockingfailure
f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
g. lvm.static vgscan --ignorelockingfailure
h. lvm.static vgchange -ay --ignorelockingfailure
i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store
NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store
NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data
partition, you can do more or less. 1 Physical Extent (PE) is 8MB.
The number after -l is the number of Physical Extents for
the partition.
p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store
NOTE: The following creates the media partition used as SDCARD and sets
it to --minor 6, make sure you set it to --minor 6, the SDCARD is
specified as dm-6 in CM7. This will save you from having to edit
/etc/vold.fstab in CM7.
s. lvm.static vgscan --ignorelockingfailure
t. lvm.static vgchange -ay --ignorelockingfailure
u. lvm.static vgdisplay
i. this command displays information on the Volume Group: store
at the bottom you should see:
Free PE/Size X / XX
where X is the number of Physical Extents free and XX is the size free.
ii. write down the number of X (Physical Extents free) to use in the
next command
v. lvm.static lvcreate -l X -M y --major 254 --minor 6 -n media store
w. lvm.static vgscan --ignorelockingfailure
x. lvm.static vgchange -ay --ignorelockingfailure
y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
zc. run webOS Doctor 3.0.0 and let it complete and let it reboot to
the language selection screen
zd. reset the HP Touchpad with [POWER BUTTON] + [HOME] and put it into
webOS Doctor recovery mode with [POWER BUTTON] + [VOLUME UP].
ze. run webOS Doctor 3.0.4 and let it complete and let it reboot and
complete webOS install and go into webOS.
If you did everything right, you now have an HP Touchpad tablet with a fresh
webOS 3.0.4 and pre-created CM7 partitions. Now, just follow the standard
CM7 install procedure after you boot into webOS 3.0.4 to install CM7.
ACMEInstaller will use the cm-system, cm-cache, and cm-data file system
you've already created. Enjoy.
webOS Doctor 3.0.0 is required. If you do not run this first, other webOS
Doctor version will fail. webOS Doctor 3.0.0 resizes and formats partitions
as needed, the other versions seem to no longer have this and fail when
the webOS partitions aren't perfect in format/size.
Click to expand...
Click to collapse

not the same method i used, but if you follow up to step "N" then doctor 3.0.0, it should be good...
still cant find that damn link! im pretty sure it was either rootz-wiki or webos-internals

Thanks a bunch guys!!!!! Will report with results when I'm done.

Worked like a charm, I can't thank you enough!

I was messing around with archLinux and messed up my TP, i tried to follow up until step N, because i want to return it back to WebOS without any Android partitions, but when it says to run Doc 3.0.0, it fails and says it was unable to restore the device. PLEASE HELP !

arseny1991 said:
I was messing around with archLinux and messed up my TP, i tried to follow up until step N, because i want to return it back to WebOS without any Android partitions, but when it says to run Doc 3.0.0, it fails and says it was unable to restore the device. PLEASE HELP !
Click to expand...
Click to collapse
Managed to fix it. Ultra happy !

Hehe, I did the exact same thing. Thanks for sharing how to rebuild the partitions.
I followed ickna11's instructions and chose to use ext3 for the CM partitions. I've noticed that the media indexer isn't working properly since the rebuild. It could just be going slow because of the different filesystem, or because I now have less than 1GB free space due to the CM partitions. Has anyone else who's done this had similar issues?

reformat nightmare
Solidus_n313 said:
not the same method i used, but if you follow up to step "N" then doctor 3.0.0, it should be good...
still cant find that damn link! im pretty sure it was either rootz-wiki or webos-internals
Click to expand...
Click to collapse
hello;
i have been trying this recovery process and it is not working from watching a youtube video, i get none of the outputs i should. the store cant be created. the ACME uninstaller and image do not complete they stall out.
i can boot into the machine from windows using novaterm, i can even see my blank partitions from the pad on the TWRP, but that is the only partition i can get to all the prebuilt commands in TWRP come back with an error that none of the partitions will mount.
any suggestions.
can i just reformat the drive, i run debian and the partitioning utility sees the partition and it shades blue when i drag over it but as i am not a tablet man i wanted to seek advice first, any help will be appreciated

reformat nightmare
ickna11 said:
You need to rebuild the partitions.
Just follow these instructions to the letter and you should be good.
Click to expand...
Click to collapse
this method has not worked for me. the store file can not be created. also, from watching a guy on youtube go through this process i get none of the responses i should get.
i was told on one forum going from cm build to AOKP build is what jacked my tab, any ideas on reformatting.

Saved my Touchpad
ickna11 said:
You need to rebuild the partitions.
Just follow these instructions to the letter and you should be good.
Click to expand...
Click to collapse
These instructions saved my Touchpad. Thanks a lot.:victory:

Similar experience to geomonroe
I too jacked my TP after flashing AOKP on top of my previously pristine CM9 1223 nightly build. I've tried this process a cople time and the "store" volume cannot be created. I get following error from command f. :
[email protected]:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
No physical volume label read from /dev/mmcblk0p14
/dev/mmcblk0p14 not identified as an existing physical volume
Unable to add physical volume '/dev/mmcblk0p14' to volume group 'store'.
I'm in over my head on this one. I need help unbricking my TP. Any suggestions?
Thanks,
Uppity

geomonroe said:
hello;
i have been trying this recovery process and it is not working from watching a youtube video, i get none of the outputs i should. the store cant be created. the ACME uninstaller and image do not complete they stall out.
i can boot into the machine from windows using novaterm, i can even see my blank partitions from the pad on the TWRP, but that is the only partition i can get to all the prebuilt commands in TWRP come back with an error that none of the partitions will mount.
any suggestions.
can i just reformat the drive, i run debian and the partitioning utility sees the partition and it shades blue when i drag over it but as i am not a tablet man i wanted to seek advice first, any help will be appreciated
Click to expand...
Click to collapse
lvm.static pvcreate /dev/mmcblk0p14
That should give you your PV back.

Hellz yeah! that worked!!!
tpsailer said:
lvm.static pvcreate /dev/mmcblk0p14
That should give you your PV back.
Click to expand...
Click to collapse
Thanks tpsailer! you rock. :good: This community is great. I hope to contribute as an expert some day. and I hope that this post helps someone else. My partition table built just fine after I used the command you suggested to recreate the physical volume.
incidentally, this you tube video was also helpful in understanding the proper responses from the commands (which were lacking in my case until I added this command.
I will also add, since it is not obvious, that I used this command directly after the vgremove command failed. then started again from the top with command a. This is probably unnecessary since the new partition table is empty after the pvcreate so you can probably start from command d. but I started from a. and was successfully able to run webosdoctor 3.0.0 afterward and recover my TP!!!! So psyched this worked.
Thanks!!!
---------- Post added at 11:31 PM ---------- Previous post was at 11:16 PM ----------
Here is the link:
https://www.youtube.com/watch?v=_btT_xomDGo
Incidentally I ran webOSDoctor 3.0.5 after running 3.0.0 and that worked just fine.
Now its time to put CyanogenMod back on this mug.
This whole problem started when I tried to flash AOKP on top of CM nightly. Any suggestions for how to properly transition from CM to AOKP?
- Uppity

Please help me out!
MikeyCriggz said:
Worked like a charm, I can't thank you enough!
Click to expand...
Click to collapse
Can you tell me exactly what you did Mikey?
Thanks a lot!

upp1tyn3gr0 said:
Thanks tpsailer! you rock. :good: This community is great. I hope to contribute as an expert some day. and I hope that this post helps someone else. My partition table built just fine after I used the command you suggested to recreate the physical volume.
incidentally, this you tube video was also helpful in understanding the proper responses from the commands (which were lacking in my case until I added this command.
I will also add, since it is not obvious, that I used this command directly after the vgremove command failed. then started again from the top with command a. This is probably unnecessary since the new partition table is empty after the pvcreate so you can probably start from command d. but I started from a. and was successfully able to run webosdoctor 3.0.0 afterward and recover my TP!!!! So psyched this worked.
Thanks!!!
---------- Post added at 11:31 PM ---------- Previous post was at 11:16 PM ----------
Here is the link:
https://www.youtube.com/watch?v=_btT_xomDGo
Incidentally I ran webOSDoctor 3.0.5 after running 3.0.0 and that worked just fine.
Now its time to put CyanogenMod back on this mug.
This whole problem started when I tried to flash AOKP on top of CM nightly. Any suggestions for how to properly transition from CM to AOKP?
- Uppity
Click to expand...
Click to collapse
How'd you flash it? In clockworkmod and applied from zip?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

ickna11 said:
You need to rebuild the partitions.
Just follow these instructions to the letter and you should be good.
Click to expand...
Click to collapse
I had recently run TPBebrick and acmeuninstaller. While trying to run WebOS Dr., I was getting the error:
Flash Failure
err -107 "Device has been disconnected. Command: run file:///usr/local/sbin/recovery/save_logs.sh"
I ran all these lvm commands & now WebOS Dr. runs fine.
Thanks for posting this!

alphabets
ickna11 said:
You need to rebuild the partitions.
Just follow these instructions to the letter and you should be good.
Click to expand...
Click to collapse
Might be dumb question, but do you type the alphabets as part of the commands or did you use them just to order the steps?

This worked!
ickna11 said:
You need to rebuild the partitions.
Just follow these instructions to the letter and you should be good.
Click to expand...
Click to collapse
Thank you! I thought my touchpad was a goner for good!
---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------
Wxanders50 said:
Might be dumb question, but do you type the alphabets as part of the commands or did you use them just to order the steps?
Click to expand...
Click to collapse
no alphabets. Just the commands. There is one step that will request you to enter several "y" answers. Just keep entering y until it stops and it doesn't ask anymore.

[Q] Touchpad seems bricked

I've been running CM9 on my 16GB Touchpad for quite a while. I flashed the newer version with camera support and again, that went well. Then I decided to flash AOKP and something happened and I can't figure out how to get back into a good state. Basically moboot comes up and shows options for webOS, CM9, AOKP, CWM, and webOS Recovery. None of the OSes will boot including webOS and the two Android entries. When I try to boot into webOS, it just shows the HP logo indefinitely. When I try to boot into either of the Android options, it just reboots after showing the splash screen briefly. When I boot into CWM it has errors like "E:Can't mount /cache/recovery/command" and I can't mount any of the other filesystems (/sdcard, etc.).
So far I've tried running ACMEUninstaller but it errors out saying "Cannot start LVM, aborting! Please reboot". I've tried "wipe data/factory reset" from CWM, but that shows a series of errors similar to the one above saying it can't mount the filesystems. I've tried to use webOS Doctor (both 3.0.0 and 3.0.5) to reimage the entire device but it says "Failed to reboot device. Contact support." I've tried these instructions:
http://forum.xda-developers.com/showthread.php?t=1426244
but after running novacom with that uImage, it doesn't go to a command prompt. As with webOS above, it just shows the HP logo indefinitely.
I've exhausted the options I could find. Any thoughts on how I might be able to get things back into a usable state?
UPDATE: I tried the linked process above again and made more progress. However, now I'm running into the same problem described here:
http://forum.xda-developers.com/showpost.php?p=32774659&postcount=129
UPDATE 2: It looks like this is exactly what's going on with my Touchpad:
http://forum.xda-developers.com/showthread.php?t=1483066&page=4
Anyone know how to get past this?

SCWells72 said:
I've been running CM9 on my 16GB Touchpad for quite a while. I flashed the newer version with camera support and again, that went well. Then I decided to flash AOKP and something happened and I can't figure out how to get back into a good state. Basically moboot comes up and shows options for webOS, CM9, AOKP, CWM, and webOS Recovery. None of the OSes will boot including webOS and the two Android entries. When I try to boot into webOS, it just shows the HP logo indefinitely. When I try to boot into either of the Android options, it just reboots after showing the splash screen briefly. When I boot into CWM it has errors like "E:Can't mount /cache/recovery/command" and I can't mount any of the other filesystems (/sdcard, etc.).
So far I've tried running ACMEUninstaller but it errors out saying "Cannot start LVM, aborting! Please reboot". I've tried "wipe data/factory reset" from CWM, but that shows a series of errors similar to the one above saying it can't mount the filesystems. I've tried to use webOS Doctor (both 3.0.0 and 3.0.5) to reimage the entire device but it says "Failed to reboot device. Contact support." I've tried these instructions
http://forum.xda-developers.com/showthread.php?t=1426244
but after running novacom with that uImage, it doesn't go to a command prompt. As with webOS above, it just shows the HP logo indefinitely.
I've exhausted the options I could find. Any thoughts on how I might be able to get things back into a usable state?
UPDATE: I tried the linked process above again and made more progress. However, now I'm running into the same problem described here:
http://forum.xda-developers.com/showpost.php?p=32774659&postcount=129
UPDATE 2: It looks like this is exactly what's going on with my Touchpad:
http://forum.xda-developers.com/showthread.php?t=1483066&page=4
Anyone know how to get past this?
Click to expand...
Click to collapse
Read this thread : http://forum.xda-developers.com/showthread.php?t=1426244&page=12
Pay special attention to page 12. It will show you how to do it without using novaterm. Also towards the beginning of the process you'll get asked a lot of questions, just answer yes to all.
Good luck.
Hold power and volume up at the same time, this will get you into correct mode (recovery).
Edit : plug your tablet in for a few hours before trying the process.

chicle_11 said:
Read this thread : http://forum.xda-developers.com/showthread.php?t=1426244&page=12
Pay special attention to page 12. It will show you how to do it without using novaterm. Also towards the beginning of the process you'll get asked a lot of questions, just answer yes to all.
Good luck.
Hold power and volume up at the same time, this will get you into correct mode (recovery).
Edit : plug your tablet in for a few hours before trying the process.
Click to expand...
Click to collapse
Thanks. Unfortunately this is actually the process I'd been trying to follow earlier and I get the exact same results through "novacom -t open tty://" that I do through novaterm, basically it fails trying to re-create the volume group 'store':
Code:
[email protected]:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
No physical volume label read from /dev/mmcblk0p14
/dev/mmcblk0p14 not identified as an existing physical volume
Unable to add physical volume '/dev/mmcblk0p14' to volume group 'store'.
If I continue working through the commands listed on that page, they pretty much all fail since they expect this volume group to exist. Any idea how to get around this issue?

Okay, I just made significant progress on this! After quite a bit of googling I found the following thread:
https://answers.launchpad.net/ubuntu/+question/15044
in particular the following from the fourth post:
Code:
My ad hoc idea: dd if=/dev/zero of=/dev/sda1 bs=1024 count=1000
...
[email protected]:~# pvcreate /dev/sda1
Physical volume "/dev/sda1" successfully created
By adding the following two steps to the process outlined at http://forum.xda-developers.com/showthread.php?t=1426244, I have webOS Doctor 3.0.0 past the dreaded 8% mark now!!!
Code:
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
Once that completes, I'll let it update to 3.0.5 and then reinstall Android, and what I feared was going to become a brick should be back into usable shape!
I hope this helps others who have encountered this same issue! Thanks again for the help!
UPDATE: I can now confirm 100% that this works. I'm installing the latest CM9 nightly to my 16GB Touchpad right now!

Glad you got it going.
Thanks for sharing your solution, I'm sure it'll help others.

really glad to hear that you got thru this..
i get spooked when ppl who know what theyre doing get hung up..
good work

I can't thank you enough for those 2 extra commands. I was able to get through and run the original batch of commands without a problem. I'm now waiting for my TP to charge enough to run the 3.0 doctor. I'm still not out of the woods yet, but I feel like I'm definitely getting there. I'll update once I get enough charge.
But regardless, thank you, thank you. I had given this thing up for a brick, but now there's some hope.
EDIT/UPDATE: This totally worked!! You just saved my TouchPad. Thank you, thank you!

brandonmarkb said:
I can't thank you enough for those 2 extra commands. I was able to get through and run the original batch of commands without a problem. I'm now waiting for my TP to charge enough to run the 3.0 doctor. I'm still not out of the woods yet, but I feel like I'm definitely getting there. I'll update once I get enough charge.
But regardless, thank you, thank you. I had given this thing up for a brick, but now there's some hope.
Click to expand...
Click to collapse
Glad to hear!!! Yeah, I was feeling the same way, so I totally understand. Mine has been running GREAT ever since going all the way through this, and I even updated it for the latest Jellybean ROM yesterday which is coming along very nicely! Please let us know if you hit anymore obstacles, or even better, if you get all the way back up and running!

SCWells72 said:
Glad to hear!!! Yeah, I was feeling the same way, so I totally understand. Mine has been running GREAT ever since going all the way through this, and I even updated it for the latest Jellybean ROM yesterday which is coming along very nicely! Please let us know if you hit anymore obstacles, or even better, if you get all the way back up and running!
Click to expand...
Click to collapse
I updated the post above, but just so no one misses it, I'm back up and running. The 3.0 doctor went flawlessly and I'm staring at WebOS right now. I'm planning on reinstalling Android here in a few minutes. Again, thanks so much! I'll come back with any questions, but for now I'm in the clear.

I would just like to say THANK YOU to SCWells72 and everyone else who is trying to help with this "Brick" issue. I was able to repair my 32gb Touchpad that would time out at 8%, with the help of the 2 extra codes.
I would like to point out something that I ran into. When I ran the 2 extra codes I bypassed the "lvm.static vgremove store" code and went right into SCWells72 codes. So, for me I did this....
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Then I proceeded to reboot into recovery and use webOS Doctor 3.0.0 to restore my Touchpad.
I hope this helps those people stuck with the same issue.

Thank you guys. Saved me I never thought I was gonna get this thing to work again. XDS members always to the rescue. Thanks everyone that had anything to do with this
Sent from my PC36100 using xda premium

Thanks so much that worked you saved my touchpad
jakkzen said:
I would just like to say THANK YOU to SCWells72 and everyone else who is trying to help with this "Brick" issue. I was able to repair my 32gb Touchpad that would time out at 8%, with the help of the 2 extra codes.
I would like to point out something that I ran into. When I ran the 2 extra codes I bypassed the "lvm.static vgremove store" code and went right into SCWells72 codes. So, for me I did this....
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Then I proceeded to reboot into recovery and use webOS Doctor 3.0.0 to restore my Touchpad.
I hope this helps those people stuck with the same issue.
Click to expand...
Click to collapse
I have tried and tried everything and this worked

dheyden said:
I have tried and tried everything and this worked
Click to expand...
Click to collapse
I'm so glad that this seems to be working for so many people!!! This community has given so much to all of us, so it's nice to be able to give a little back, even if it's basically just standing on the proverbial shoulders of others and stumbling into something that actually worked...

dheyden said:
I have tried and tried everything and this worked
Click to expand...
Click to collapse
Hey, I'm glad my post helped you.

Think my TP is bricked as well. installed the recent CM10 preview, and hit an infinite boot loop. When I tried the reboot the screen went black, and now I can't get a thing to trigger on the device. No reboot, no blinking command buttons, no USB cable recognition on my PC - just an ice cold black touchpad.
I'm thinking about leaving it sit for a week and let the power completely drain. Maybe coming back to reboot it later, I'l be there for a power signal and get into TWRP or something. Other idea is to leave it plugged in for a few hours, and see if I can force a reboot.
Any ideas out there on this one?
--McBean

SCWells72 said:
Okay, I just made significant progress on this! After quite a bit of googling I found the following thread:
https://answers.launchpad.net/ubuntu/+question/15044
in particular the following from the fourth post:
Code:
My ad hoc idea: dd if=/dev/zero of=/dev/sda1 bs=1024 count=1000
...
[email protected]:~# pvcreate /dev/sda1
Physical volume "/dev/sda1" successfully created
By adding the following two steps to the process outlined at http://forum.xda-developers.com/showthread.php?t=1426244, I have webOS Doctor 3.0.0 past the dreaded 8% mark now!!!
Code:
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
Once that completes, I'll let it update to 3.0.5 and then reinstall Android, and what I feared was going to become a brick should be back into usable shape!
I hope this helps others who have encountered this same issue! Thanks again for the help!
UPDATE: I can now confirm 100% that this works. I'm installing the latest CM9 nightly to my 16GB Touchpad right now!
Click to expand...
Click to collapse
Ok I got to run the webOSdocotr, but I get stuck at 8%. I cannot figure out what to do. What did you do exactly to fix this???

ScottBroker said:
Ok I got to run the webOSdocotr, but I get stuck at 8%. I cannot figure out what to do. What did you do exactly to fix this???
Click to expand...
Click to collapse
I did something, and now TWRP wont boot up either. Just the HP logo. I get it into recovery, and try AC%. A webosdocotr, and boots me out at 8% MEuninstaller and it says abort LVM not there.... Any suggestions?

Same problem here with a 16GB Touchpad. But, when I input:
Code:
lvm.static vgremove store
NOVATERM says:
Code:
Volume group "store" not found
What can I do ?
Edit: found out !

Thank you so much
SCWells72 said:
Okay, I just made significant progress on this! After quite a bit of googling I found the following thread:
https://answers.launchpad.net/ubuntu/+question/15044
in particular the following from the fourth post:
Code:
My ad hoc idea: dd if=/dev/zero of=/dev/sda1 bs=1024 count=1000
...
[email protected]:~# pvcreate /dev/sda1
Physical volume "/dev/sda1" successfully created
By adding the following two steps to the process outlined at http://forum.xda-developers.com/showthread.php?t=1426244, I have webOS Doctor 3.0.0 past the dreaded 8% mark now!!!
Code:
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
Once that completes, I'll let it update to 3.0.5 and then reinstall Android, and what I feared was going to become a brick should be back into usable shape!
I hope this helps others who have encountered this same issue! Thanks again for the help!
UPDATE: I can now confirm 100% that this works. I'm installing the latest CM9 nightly to my 16GB Touchpad right now!
Click to expand...
Click to collapse
Dude....you should have a donation button set up. I've been struggling with my TP for 3 days with no luck. Then I found your post here, and those 2 extra lines of code you shared saved the day. I have flashed cyanogen at least a dozen times with no problem, then I tried some hybrid combo of cyanogen and aokp...boy that was a mistake. I'll stay with jcsullins from now on for sure. Thanks for sharing, I'm sure you have helped a lot of people with this.

spunout62 said:
Dude....you should have a donation button set up. I've been struggling with my TP for 3 days with no luck. Then I found your post here, and those 2 extra lines of code you shared saved the day. I have flashed cyanogen at least a dozen times with no problem, then I tried some hybrid combo of cyanogen and aokp...boy that was a mistake. I'll stay with jcsullins from now on for sure. Thanks for sharing, I'm sure you have helped a lot of people with this.
Click to expand...
Click to collapse
Can you say what hybrid you flashed so that I or others can stay away from it if we wish . Or pm.

[Q] bricked tried everything no store file

went from cm9 nightly to AOPK.
bootloader is there can only access TWRP.
TWRP, error /sd card will not mount.
os doctor failed restore.
nothing but TWRP accessible from bootloader.
file manager shows all files empty. no backups accessible.
is this recoverable?
followed this numerous times:
This is for all those people who want to start over. I made the mistake of using webOS Doctor without removing the Android and Linux partitions. That left me with a deer turd for an HP TouchPad. So after about 2 hours of slaving, I figured out what to do
I. What you need
Novacom - Click
Novaterm - Click (or found in C:\Program Files\Palm, Inc\terminal. Run novaterm.bat)
Recovery uImage - Click
WebOS Doctor 3.0.0 - Click
WebOS Doctor 3.0.4 (optional) - Click
II. What to do
1) Install Novacom and extract Novaterm.
2) Open a command prompt and navigate to your Palm, Inc folder (usually \Program Files\Palm, Inc)
3) Move the recovery uImage to the Palm, Inc folder.
4) Boot your Touchpad into recovery (Power + Volume Up from power off)
5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage ) (without the parenthesis)
6) Once run, all you'll see on the Touchpad is the HP logo. This is good. Now open Novaterm and hit Connect
7) If you see a prompt that says something like "[email protected] device" this is good, now run these commands IN ORDER and these commands are CASE SENSITIVE
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 1618 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
I get a store error at the start it does not see the store folder and can not figure how to create one what is my next step. I can not youtube myself out of this one i need help I miss my touch pad I love my nexsus 10 but the TP had a sort of cult following I need it in my life

I know you aren't bricked yet, but you could try TPDebrick by jcsullins. Just google it.

I got it
Wow I finally got it to work in my stupidness I figured out what i was doing incorrectly l
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store and then I would get a error message about parseing error I was putting a number 1 for the -l 71 instead of the l my mistake my touch pad is up and working and I am ready to install cm10 on the puppy

[SOLVED] TouchPad Bricked! - Formatted using Windows...

Hello all,
Unfortunately, when Windows asked me to format the TouchPad, my first question was not "Why?" (as it normally is with everything else ). I just did it.
Now, I have a TouchPad that:
1.) Doesn't boot WebOS or Android, and is therefore...
2.) Bricked...?
I have tried the following:
1.) Ran tpdebrick v004 by RolandDeschain79
Successful (It returned "All Done"); WebOS Doctor still had issues though: "We could not recover your device."​2.) Tried rebuilding the file system - http://www.webos-internals.org/wiki/How_To_Recover#Complete_filesystem_creation
Not successful; Now hangs at the palm.com/rom screen with the exclamation point​3.) Tried running these magical commands (lvm.static vgscan --ignorelockingfailure, lvm.static vgchange -ay --ignorelockingfailure, mkdosfs -f 1 -s 64 -F 32 /dev/store/media) via Novaterm (and "novacom -t open tty://")
1st command: Reading all physical volumes. This may take a while...: If by a while it meant a millisecond, then I guess it went okay. Didn't return anything though.
2nd command: Basically just returned the same thing I typed.
3rd command: /dev/store/media: No such file or directory.​4.) Pretty much every other fix I could find through Google.
Didn't work.​
I should also note that running things like pvscan, lvscan and fstab though novaterm.
Any help on the matter is greatly appreciated. I have another TouchPad that I can restore from if anyone thinks it will help anything. It was configured almost identically to this one (both are 32GB).
Thanks!
EDIT: SOLVED!
SCWells72's post and rr5678's thread solved my problem after retrying the commands in novaterm for what seems like the millionth time!
To sum it up:
Novacom boot the TP with the topaz recovery image, open novaterm, and enter the following commands (in this order!):
These are the first two commands to send. They are what solved my problem...
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14​
NOTE: THIS IS FOR THE 32GB TOUCHPAD ONLY!
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgremove store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media​
Again, those commands are for the 32GB TP. See rr5678's thread for more specific information as well as the code for the 16GB version!
Hope that helped someone else! I know this is all around the web already, but I just wanted to post my results here for future reference.

Read this and the comments on page 12, it saved me.
http://forum.xda-developers.com/showthread.php?t=1426244

sstar said:
Read this and the comments on page 12, it saved me.
http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Tried it. Same result.
The "store" volume group is not found and the commands error out with "No such file or directory" or command unknown.
Still though, I appreciate the suggestion!

Re: [Q] TouchPad Bricked! - Formatted using Windows...
I did this once, it was a real bugger to fix... let me try to remember what I did!
Sent from my Touchpad using xda premium

-SGA- said:
I did this once, it was a real bugger to fix... let me try to remember what I did!
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
I hope you can remember!
Pretty close to declaring it bricked for good!

Guess what!?
IT'S BACK!
I decided I'd try these instructions again (which popped up all over the place in regards to un-bricking this thing) and sure enough, this time, the mkdosfs command DIDN'T throw back the "No such file or directory" error!
I changed absolutely nothing since the last time I did it, which is weird. But I'm not complaining!
Thank you very much for your help!

[Q] HELP!! Error while rebuilding partition on "bricked" TOUCHPAD

Hey everyone,
the little brother somehow jacked up the touchpad. It had CM9 as well as WebOS previously. Its been sitting as a paper weight for the past 4 weeks.
I found and followed this thread
http://forum.xda-developers.com/showthread.php?t=1564938
HOWEVER,
after i run the
"lvm.static vgremove store"
I get the following error: "cant remove open logical volume "media" "
ANY HELP WOULD BE GREATLY APPRECIATED.
Thanks.

ace08401 said:
Hey everyone,
the little brother somehow jacked up the touchpad. It had CM9 as well as WebOS previously. Its been sitting as a paper weight for the past 4 weeks.
I found and followed this thread
http://forum.xda-developers.com/showthread.php?t=1564938
HOWEVER,
after i run the
"lvm.static vgremove store"
I get the following error: "cant remove open logical volume "media" "
ANY HELP WOULD BE GREATLY APPRECIATED.
Thanks.
Click to expand...
Click to collapse
Try this guide : http://forum.xda-developers.com/showthread.php?t=1426244
If you have problems with novaterm, there is a workaround on page 12.
Make sure you have a fully charged battery, you don't want to run out of power while doing the procedure.
Good luck.
Edit: it's basically the same guide. There's a thread here somewhere where they solve this. A search should turn it up.

Thanks for the help so far guys....you are all wonderful people...
I am trying to run novaterm and I keep getting error messages on each key stroke...
i am probably missing something very easy (typical me)...currently searching for it on XDA...figured id post here too just in case one of you has a simpler solution...
I have attached a screen shot of the error im getting in NOVATERM
after some searching I found that I could just forgo the novaterm and use novacom via (http://forum.xda-developers.com/showthread.php?t=1426244&page=12)
however once I do the
"After doing the novacom mem...... command
Type novacom -t open tty:// "
and start going step by step on the procedure....i get ANOTHER ERROR(thumbnail titles "error2")....
apparently "store" isnt there....
I will keep searching but I'd love some input as I am traveling this weekend and would like a tablet to kill some time with.

PROGRESS
OK...so after much much searching I have come across the following
http://forum.xda-developers.com/showthread.php?t=1971859
"{Code:
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14 }"
So now that I did that, I moved all the way to step "I"
a. lvm.static vgscan --ignorelockingfailure
b. lvm.static vgchange -ay --ignorelockingfailure
{c. lvm.static vgremove store} ----GOT REPLACE WITH THE ABOVE CODE
d. lvm.static vgscan --ignorelockingfailure
e. lvm.static vgchange -ay --ignorelockingfailure
f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
g. lvm.static vgscan --ignorelockingfailure
h. lvm.static vgchange -ay --ignorelockingfailure
i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store
However once I type it in to novacom, I get an error stating
"redundant stripes argument: default to 1"
If anyone could lead me in the right direction, id highly appreciate it.
THANKS ALOT

THREAD DELETED!!!!
DELETE!!!
admin plz delete this thread thank you