yashsingh1/xdaforums huggingface dataset:
[TouchPad General] Hazeno:
I have used this twice, And last night decided to go back to factory, as Android kept deleting Installed games for no reason.

Followed it as usual, and came to an error i have never seen before. When doing

lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store

And all the rest, it would give Invalid sector, Minimum 1? I think that was the error. Since i was already in and had deleted store, i decided to carry on,

Did the WebOS 3.0.0 install, As it rebooted itself it hung on HP logo. So i did a hard reset and it booted to 3.0.0.

Updated to 3.0.5 via Wifi, and it crashed while installing. So had to manually install 3.0.5, which had to have a force restart before booting.

Just wondering if i should go back through again?

ALso just noticed, fist boot of 3.0.0 it wouldn't restore my WebOS data, Second boot it did. With 3.0.5 It has done the exact same.

Also does anyone have a link to a Novaterm that actually lets you copy and paste? Or is there a .bat to use? I wouldn't mind using a .bat to do it all. Or a simple method of doing it. I am rusty using batch commands!
[TouchPad General] rr5678:
I think the novacom in the Palm, Inc. folder lets you copy and paste (but only with control+c & control+v).
[TouchPad General] LBCaptivate:
How did you get Web doctor 3.0 to work? When I try to double click it, it opens as a zip. I tried to change the extension to jar but I still get the same thing. When I turn on the TP I get stuck at the HP logo. I can get to USB mode but the only way the TP will turn off is if I hold power+ volume and push the home button 15 times. Help??
[TouchPad General] LBCaptivate:
How did you point Novacom? What commands did you use?
[TouchPad General] LBCaptivate:
Thanks OP!!!! I finally got it to work.
[TouchPad General] tribecca:
Store already exists

Has anyone solved this problem? I tried everything in this thread.
[TouchPad General] fouad796:
im stuck in the same problem too
[TouchPad General] ace08401:
ANY HELP

hey everyone,

after two days of searching, I decided to post a new thread up and delete the old one.

I have gotten past the initial stages of the restoration process. However, i keep getting stuck at step outlined in RED

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 keep getting the error "redundant stripes error: default is 1"

IF SOMEONE COULD PLEASE HELP ME OUT. I WOULD HIGHLY APPRECIATE IT .

THANKS
[TouchPad General] iamatechnoob:
I have my touchpad in factory condition now but I see that I have only 12.6gb of free space in my 16gb touchpad. I read elsewhere that the free space should be 13.6 by default. I have downloaded Tailor from preware, but I have no idea how to use it to check/repair/fix whatever needs fixing. Anyone can help? :/
[TouchPad General] post-mortem:
I haven't used it, but I thought the help (or a link to the wiki) was built into the app.

Maybe this could help?

How to guide for changing your system, data, and cache partition sizes to whatever you want.
[TouchPad General] iamatechnoob:
Thanks for the link, but eh.. my entire USB (Media) partition is only 12.6 at its max. My max partition size is 12952mb only. Minus off webOS system files and crap, 12.6 is what I get. I wonder if its because of webos 3.0.5 or there's something wrong with the internal partitioning of the sd card...
[TouchPad General] valdeezelhoff:
I am trying to fix a touchpad that has a looping bootloader (3.5). Whenever one of the Moboot options to load CWM, WebOS, or CM are selected it just reboots back to Moboot and will not boot WebOS or Android. I performed the ACMEUinstaller (Device in WebOS recovery mode and use the novacom and CMD option) and it appeared to perform the log action but then suddenly the entire screen goes blue and it reboots back to the boot loader. I've ready thread after thread and I've tried to process the steps in this thread but it just reboots back to the boot loader so when I get to the step of using Novaterm it doesn't distplay "root@WebOS" or anything.

Can anyone point me in the right direction? I can usually find my way to solving a problem but I am confused on this one.

Thanks in advance!

HP Touchpad - 32GB

Version of CM: unknown

Moboot 3.5

I would like to continue to use Android on this device and if I have to restore to factory and then start all over I am fine with that, I just don't want to brick this thing.
[TouchPad General] valdeezelhoff:
Dang not even a Noob burn or anything, that's cold blooded. heh
[TouchPad General] chicle_11:
There's a workaround on page 12, if you're having trouble with novaterm.

Good luck.
[TouchPad General] geomonroe:
Try the palm, Inc. Folder by way of program files. I have better luck with novaterm from there. Also make sure your battery is completely charged, it matters;)

John 3:16
[TouchPad General] valdeezelhoff:
I've pretty much exhausted every procedure i've come across online and it keeps doing the same thing. I think the partitions are either jacked or have been erased. *shakes head*
[TouchPad General] geomonroe:
OK, let me track down the post I used once, its just two lines, and it got my tp to cooperate with this process

John 3:16

---------- Post added at 10:45 PM ---------- Previous post was at 10:17 PM ----------

ok found it.

http://xdaforums.com/showthread.php?p=34146652#post34146652

the link at #2, starting at post 21, the warning about fsck scared me so i didnt do it. and some how i think this is what helped me once.

P.S. dont take this wrong just refreshing the basics. make sure pad is charged i usually let it sit for 24 hours after one of my last incidents.

useing the stock charger and a good heavy guage usb chord will also help. i dont know why but the tp is very sensitive to the correct voltages it needs to charge. let me know how it goes.

george
[TouchPad General] valdeezelhoff:
After I process the 'novacom boot mem' command the tablet reboots back to the boot loader so when I run the 'novacom -t open tty://' command it says "device not found".

---------- Post added at 09:01 AM ---------- Previous post was at 08:43 AM ----------

Instruction noted, i'll let it sit on the wall charger for the next 24 and repeat these steps and see what happens haha. I hope the problem is me being impatient and overlooking a step because that'll mean the issue can be resolved so stay tuned for tomorrow'w episode of "Impatient Noob over looked a step which prevented him from getting to the root@webOS device part"
[TouchPad General] geomonroe:
I have been through this a few times, so the noobs are not alone;)

John 3:16
[TouchPad General] valdeezelhoff:
Tried again after over 24 hours of recharging the device, connected to the touchpad via Novaterm and ran [battery status] and it displayed a percentage of 98. I followed the instruction again and it takes the command which changes the screen from the USB recovery mode to the HP boot logo. Then the device reboots again within 5 seconds and its back to the boot loader screen.

http://youtu.be/MRLKHQIv-GA
[TouchPad General] geomonroe:
OK that stinks, I have not had that. There is a HP tp guru over at the webos sight. Let me find him. Also, if it were me I would pm the guy from the link I sent you the other day. I am sure if you can get to the boot loader some one will be able to get you recovered:)

John 3:16
[TouchPad General] valdeezelhoff:
ewtflyi map

Yea I had a feeling this might be a special situation. Thanks for your help thus far and for passing it along. I'll send PM the guy you mentioned and see what he has to say.
[TouchPad General] geomonroe:
Boot Loop

hey i was rereading your post to make sure i didnt miss anything.

i am wandering if you can boot into recovery mod webos style. either from moboot or hard reset style. there have been times when my tp was so fickle i would hold all three buttons. vol. up. etc.. until i got the hey stupid let go of the buttons message, anyway if you can run webos doc. 3.0.0.

not trying to be a pain just dont want to miss the easy stuff:cyclops:
[TouchPad General] valdeezelhoff:
I'll try it in about 30 minutes and let you know.
[TouchPad General] valdeezelhoff:
Okay so after holding all three buttons down for probably 5 minutes (It flashed a blue screen right before the screen turned off) it didn't display any messages, just what appeared to be a powered down touchpad but when I plugged the usb cable into the computer windows recognized the device and began trying to install a driver but failed.
[TouchPad General] geomonroe:
Drivers

ok, that sounds good. so what would happen if you recharged and tryed to boot into recovery with power button and volume up.

i hold my pad with power on upper left and that gives me the rocker button on top left, so holding only the left side of the long switch on top and the power button should get you into recovery. try this, hopefully you get the big usb symbol.

https://code.google.com/p/universal-novacom-installer/

this is the link for novacom drivers. it has the novacomd and novacom and xterm. but you are not there yet. if it were me i would download

http://www.webos-internals.org/wiki/WebOS_Doctor_Versions

that is where i would start when and if you get the big usb symbol.

the guy from the first post makes a comment about 3.0.0. being the doctor version that can fix partitions.

please dont be offended if i am talking to basic. i am not really technical, and i dont like reading posts when i am asking for help and there is too much implied knowledge going on. i just want to be thorough:D

oh by the way here is the guys info i was telling you about from WebOS Nation.

http://forums.webosnation.com/members/532320.html
[TouchPad General] rr5678:
When it jumps back to moboot, select boot WebOS recovery and try again.
[TouchPad General] hovax615@hotmail.com:
WiFi isn't working on mine on android ROMs i was watching something one day on cm9 and all of a sudden it stopped. Then when I tried to get back on it was searching for WiFi “turning WiFi on" but stayed stuck there. I did acme uninstaller and flashed it 20-30 different times cm9 cm10 schizoid all different roms and still no WiFi. I also did webos doctor and it still didn't work. Webos the WiFi is fine but not android.
[TouchPad General] thetank225:
Having major issues

Hey everyone,

I first want to say that I love this forum, it's a huge help to people like me. But I am having some major issues, but its probably just user error on my end and I am wondering if I could get some help.

I downloaded everything that you had listed and added it appropriately. The first time I tried to hit connect on the novaterm, it wouldn't do anything. So I disconnected my tablet, shut if off and tried it again, but now when I go to run the command prompt, and hit enter after adding the "C:\Program Files\Palm, Inc novacom boot mem:// < nova-installer-image-topaz.uImage" it gives me the message of "failed to connect to server".

I shut down my tablet and turned it on and as soon as the black screen appeared I held the volume up button and it went to the USB drive mode and tried it numerous times, what am I missing here? I greatly appreciate your guys help, I actually feel like I know what I am doing....until I run into something like this.

Can someone please help me with this?? I feel like an idiot not getting this thing to go past this.
[TouchPad General] geomonroe:
I go to the terminal through the palm inc file itself not through the terminal, don't remember the path exactly, just look around in the palm,inc file and you will find it.

P.S. if you use Ubuntu 12.04 LTS there are some great instructions for getting the tp tools set up

blah blah blah
[TouchPad General] thetank225:
Thanks. I will try that.
[TouchPad General] ReikiDraven:
You're a giant among men, brother. This was the only thing that would have fixed my new Touchpad. You ended a solid 25 hours of torment for me. Thank you.
[TouchPad General] geomonroe:
I hope you mean me cause I just got served for flaming so my ego is shakin :o
[TouchPad General] bigmks:
Interesting theory. I dusted off my TP, ran the command and got back the same code you posted. What's next?
[TouchPad General] nlra:
Hey there. So your CSD register contents match mine exactly? What if you were to post the entire thing here anyway just in case there is a subtle difference you might be missing?

I don't see any prior posts from you on XDA, so I'm not sure what the specific symptoms are with your TouchPad. Do they match those described by the other people I was addressing in my response? (This thread covers many different modes of TP failure.) Specifically...

When you run either WebOS or Android, nothing you do (settings changes, downloads, new app installs, local document saves, etc.) is "remembered" after a reboot?

When you attempt to wipe and recreate all of the logical volumes as documented at the beginning of this thread, you issue the "lvm.static vgremove store" command, followed by "lvm.static vgcreate -s 8M store /dev/mmcblk0p14", and the second command returns to you this error?: "/dev/store: already exists in filesystem", and "New volume group name 'store' is invalid"

If these don't apply to you, then my post does not address your problem.

-- Nathan
[TouchPad General] bigmks:
Yes, I'm a long time reader but first time poster.

But the issue that I am encountering with my TP is exactly what you describe above. When attempting to remove and recreate the volume store, it does error that the store already exists.

I ran the command you provided from the terminal app in CM9. It returned the following value:

d00f00320f5903ffffffffff92404010

---------- Post added at 09:52 AM ---------- Previous post was at 09:45 AM ----------

Yes, if I make any changes in CM9 or webOS then reboot the TP, it does not save any of the changes made.
[TouchPad General] rr5678:
If I'm not mistaken, doesn't file system damage make Linux lock the drive in read-only mode?
[TouchPad General] nlra:
Well, then we might be back to the drawing board here. It doesn't appear that the whole-flash write protect has been engaged. There *is* apparently another way that the documentation describes, though, to write-protect only certain parts of the flash chip. This would be accomplished by manipulating certain parts of the EXT_CSD register. Unfortunately, it does not look like EXT_CSD is exposed by sysfs. I will have to do a little bit more reading up on this.

One thing you could try to do to see if indeed the flash chip is write-protecting itself would be to attempt to blank out the first sector of data on it (boot sector?). If you do this and it is successful, it will put the TouchPad into QHUSB-DLOAD/Qualcomm Download Mode, at which point you would run TPDebrick on it. This will not have any effect if the flash chip is indeed write-protected in some way at the hardware level of things. At this point, you probably don't have anything to lose by trying it: perform the bootup procedure described at the beginning of this thread in the OP, and then once you get to the point where you are about to start entering in the various lvm.static commands, run this single command instead (WARNING: I have not vetted this procedure myself! This could brick your TouchPad! I am not responsible if it does!):

dd if=/dev/zero of=/dev/mmcblk0 bs=512 count=1

...then reboot your TouchPad. If it boots up normally, then the flash chip is hardware-write-protected somehow. If all you get is a blank screen at this point, then it actually worked! At this point, Google for "TPDebrick v004" (I'd post the link to it myself if my account on this forum was not still restricted), follow the procedure, and once it is finished, go into bootie mode and run WebOS Doctor 3.0.0 on your TouchPad.

You're mistaken. Most UNIX-like systems will mount various volumes read-only until after filesystem integrity has been determined, at which point they will be re-mounted read-write. So filesystem damage that is not automatically correctable (e.g., a fsck triggered during boot cannot fix the volume) would cause the re-mount simply to not occur, and the system would also likely boot straight into single-user mode if the affected volume is the boot volume. But this all happens at the *volume* (partition/filesystem) level, not at the physical *drive* level; no kind of drive "locking" occurs. It would be absurd for an OS to do this, or for the hardware to enable it to do so. Think about a multiboot PC: hypothesize that Linux filesystem corruption occurs, so Linux locks the drive, thus preventing you from using the copy of Windows that is on there, even though it is in perfectly good shape? What a mess that would be.

-- Nathan
[TouchPad General] rr5678:
You've gotta consider this though: Most TouchPads this issue occurs on ARE multi-boot and it does affect both operating systems. Maybe eMMCs are handled differently. Hell, maybe it's the controller screwing everything up. I'd make a more detailed reply right now but I'm going underground :p
[TouchPad General] nlra:
That's actually kinda my point: it's not "the OS" doing it because there is > 1 OS involved here.

In an eMMC design, the controller is part of the flash chip.

In a multi-OS system, with all OSes being unable to write to the drive, the write-protect is obviously happening in hardware, not software. Heck, when you follow the procedure in the OP, you aren't even booting one of the OSes that resides on the flash: you're basically booting a recovery image via USB, and you STILL can't write to the drive from that environment.

The only documented way of write-protecting an MMC-class flash device (besides SD cards with their write-protect slide switch) is via manipulating writable bits in the CSD and EXT_CSD registers. And if an OS is touching those things, that's not a feature: that's a bug. Unless the engineers were high when they made that decision, there's no way that was intentional.

-- Nathan
[TouchPad General] jshafer817:
Yep.. I did that once... sucked.. great guide! I was lucky.. I have 2 touchpads and I got to look at the stock touchpad to look at the partition layout. Great guide! Now I can not feel the need to keep it so stock.
[TouchPad General] os2baba:
I think my son inadvertently installed the nightly build downloaded by goomanager. He doesn't recall what he did. But it can't get beyond the cyanogenmod face logo. I can boot into WebOS. But the file system is read locked. I can make changes to the sd card when connected to the PC. As soon as I disconnect, it reverts back. I tried formatting the sd card. No go. I'm afraid I have a "safe mode" TP now :(

I was able to install Preware and Tailor once using WebOS Quick Install. But I'm unable to repeat that. If I were to go into WebOS recovery and run Novaterm, can you tell me the equivalent command to run from Novaterm?
[TouchPad General] nlra:
The command is the same. Did you try it?

-- Nathan
[TouchPad General] daddyspc:
Thank You , Thank You....

ok, I have this exact problem...and I have also tried every damn thing on the net for the last 6 months trying to get my sd to work right again and write. So let get down to the brass tacks...

I just ran that code line through my terminal and received the exact same code you have....

Code:

d00f00320f5903ffffffffff92404010

so I also have a 4....let me know what else I can do to help move this along!
[TouchPad General] sokratz:
Thanks for the guide. Having some odd issues and may want to go back to scratch.
[TouchPad General] geomonroe:
NIRA that is some impressive research. In motor controls there are also soft and hard lock outs. From what I have seen my tp do, I can't prove it but I swear low charge will put the tp into a soft lockout situation, so before any fixes are tried at least a twelve hour charge time on the stock if not larger gauge chord is a must.

Second, I have trashed my pad numerous times but I can't get to the link I want to share so I will try to get it tomorrow. I think it may help the two previous posters.
[TouchPad General] geomonroe:
this thread post #163
[TouchPad General] SAITEJA PARSI:
Thanx for ur help

its working...

but 1 doubt

after the 3rd step in novaterm it is asking like this

Do you really want to remove volume group "store" containing 11 logical volumes? [y/n]

what should I prefer, yes or no??

---------- Post added at 11:58 PM ---------- Previous post was at 11:28 PM ----------

Thanx for ur help

its working...

but i doubt

after the 3rd step in novaterm it is asking like this

Do you really want to reove volume group "store" containing 11 logical volumes? [y/n]

what should I prefer yes or no??
[TouchPad General] geomonroe:
I say yes for all of them after all your rebuilding the system

sent from the bathroom ;)
[TouchPad General] SAITEJA PARSI:
thanQ

I got it :)
[TouchPad General] geomonroe:
Another thing to remember. If you use Windows when working with your tp remember to eject it correctly. I read somewhere that if you don't it can damage the partitions. Don't know for a fact, but why chance it. Best eject is from computer tab not sys trey

;)

sent from the bathroom ;)
[TouchPad General] SAITEJA PARSI:
thanQ dude..

thanx 4 ur help :) :good:

I successfully got my tp back after few months..

Now its working properly.

Thanx 1ce again :)
[TouchPad General] thecellman:
I tried this and it did not work. **Sigh*** I was really hopping it would. Thanks for the very useful info..I'm hoping this is getting closer to a solution.
[TouchPad General] null0pointer:
I've been posting off and on since 2012 trying to get my read-only Touchpad working. I broke it out the other day in hopes of reviving it.

Some basic facts about what I'm experiencing:

- Does not boot WebOS at all.

- Stuck at HP logo till battery dies

- When powered off, it will automatically power itself back on and get stuck at same HP logo

- No Android loading was ever even attempted

- I can get to the recovery mode "USB Logo" boot by holding down Power-Home-Volume Up

- WebOS Doctor recovery dies at 12% no matter what

- I've tried using the Guide at the start of this thread and everytime I rescan, it finds the "store" yet again, even after I've deleted it.

- I've also tried SCWells72 suggestion **

root@webos-device:/# lvm.static pvcreate /dev/mmcblk0p14
Can't initialize physical volume "/dev/mmcblk0p14" of volume group "store" without -ff

I then tried adding "-ff" and it errors as follows:
root@webos-device:/# lvm.static pvcreate /dev/mmcblk0p14 -ff
Really INITIALIZE physical volume "/dev/mmcblk0p14" of volume group "store" [y/n]? y
Can't open /dev/mmcblk0p14 exclusively. Mounted filesystem?

** As pasted above, it still doesn't work.

When I run the cat command listed earlier I get the same result as everyone experiencing issues:

d00f00320f5903ffffffffff92404010

I've spent way too much time trying to get this to work... might be time to just eBay it or trash it.

Any thoughts or suggestions?
[TouchPad General] rr5678:
If you decide to trash the unit, do you think you can send it my way? It would be the perfect unit to poke and prod in search for a solution.