Hi guys,
I started having this issue that every-time I use the Touchpad on CM9 or WebOS it just freezes and reboots/resets...
Take a look:
No mater what I do (I've tried this souldevteam.net/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad it always goes back to reboot/reset loop as soon as I start to use it.
I have this Touchpad since new and never had any issues in the pass.
I would like some pointers in what can I do to repair, is the problem at the mainboard? memory? hdd? I could use this place to get parts: portatronics.com
Thanks!
It does it both in CM9 and WebOS? If so, I'd just run the ACMEUninstaller, run WebOS Doctor and once thats all finished, boot into WebOS (DONT install Android yet) and see if it continues bootlooping.
This thread may be of use to you. http://forum.xda-developers.com/showthread.php?t=1564938
allstar319 said:
It does it both in CM9 and WebOS? If so, I'd just run the ACMEUninstaller, run WebOS Doctor and once thats all finished, boot into WebOS (DONT install Android yet) and see if it continues bootlooping.
This thread may be of use to you. http://forum.xda-developers.com/showthread.php?t=1564938
Click to expand...
Click to collapse
Yes on both, same thing:
I did use ACMEUninstaller and then wiped the partitions:
Code:
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
Then I do a WebOS 3.0 then 3.05, same thing.
I guess it is highly probable to be a Hardware problem, do you know who can fix this besides HP?
Thanks!
Jor3lBR said:
Yes on both, same thing:
I did use ACMEUninstaller and then wiped the partitions:
Code:
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
Then I do a WebOS 3.0 then 3.05, same thing.
I guess it is highly probable to be a Hardware problem, do you know who can fix this besides HP?
Thanks!
Click to expand...
Click to collapse
Sorry, nope. Unless someone else can think of a way to fix it, seems it could be a hardware issue. If you're still in warranty, just open up a request with HP and ship it to them. Just be sure to wipe Android completely. If not, search around town and see if any of those phone repair shops can take a look at it or see if HP can fix it for a price.
allstar319 said:
Sorry, nope. Unless someone else can think of a way to fix it, seems it could be a hardware issue. If you're still in warranty, just open up a request with HP and ship it to them. Just be sure to wipe Android completely. If not, search around town and see if any of those phone repair shops can take a look at it or see if HP can fix it for a price.
Click to expand...
Click to collapse
Well I bought it in 12/2011 as a Refurb, so it's out of the warranty.
I could try here but nobody seams to ever heard of this store: www portatronics com
when did it start doing this? before or after you flashed CM9? If it didnt always do this, then it's likely not a hardware issue. if not then try to think of what changes you made that may have done this.
SOLVED
haxin said:
when did it start doing this? before or after you flashed CM9? If it didnt always do this, then it's likely not a hardware issue. if not then try to think of what changes you made that may have done this.
Click to expand...
Click to collapse
Hi I was able to fix it finally!
Because I paid $115 refurb for this brand new I didn't want to send anywhere to pay over $200 for repairs...
So I followed this guide:
HP TouchPad Take Apart Repair Guide Be careful not to brake the clips!
After opening the TP I removed the mainboard only.
I placed the mainboard only inside a non-stick foil paper and placed it in the oven at 395o.F for 10 minutes (like I used to do to my broken video cards in the old days)...
After that I let it rest and the following morning I put everything back together!
Amazingly the TP powered up right away and now is free of the reboot loop issues!!!!!! :evil:
I couldn't believe it but it did work.
My conclusion is that is was a hardware error, most likely weak solder joints in the MB.
That's awesome.
Related
======================================
Story to explain how I partially "bricked" my touchpad
======================================
I say partially because WebOS wouldn't boot but I could get into recovery
It started out when I put Android on my touchpad. It worked perfectly.
The next day, I suddenly couldn't edit any files on Android, so I hooked it up to my computer. Windows said I should reformat it. So I just let windows reformat it to fat32.
After the format, something odd happened. I wasn't sure what was going on, but basically:
Android was able to write to the SD card now, but when I plugged it into my computer to look look at the files, it showed me what windows formatted. Same happened when I booted to WebOS.
So great, now I have created myself a problem.
Attempting to fix it, I decided to uninstall android and run webos doctor. Didn't fix my problem.
I then proceeded to "recreate the filesystem" with these commands.
Code:
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
Well, I caused myself a bigger problem. Now WebOS won't even boot.
======================================
Trying to figure out what went wrong
======================================
Great, my touchpad won't boot.
I tried to doctor it, and it get's stuck at 8%. I checked the logs and found this bit of useful information
Part of doctor log
Code:
INFO: Unmounting /dev/mapper/store-log
Oct 24, 2011 3:53:09 AM com.palm.nova.installer.core.MountUtils umountPart
WARNING: MountUtils: unmount failed, retrying in 1 second
Oct 24, 2011 3:53:10 AM com.palm.nova.installer.core.MountUtils umountPart
SEVERE: MountUtils: unmount failed: umount: can't umount /dev/mapper/store-log:
No such file or directory
So I went back to root access and tried to mount all partitions.
mount -a
Code:
mount: mounting /dev/mapper/store-var on /var failed: Invalid argument
mount: mounting /dev/mapper/store-log on /var/log failed: Invalid argument
Turns out this is the real reason doctor failed.
I then checked everything I could to see if i could find any other problems
pvscan
Code:
Filesystem Size Used Available Use% Mounted on
/dev/root 28.8M 21.2M 7.6M 74% /
/dev/root 28.8M 21.2M 7.6M 74% /dev/.static/dev
tmpfs 2.0M 108.0K 1.9M 5% /dev
tmpfs 32.0M 0 32.0M 0% /tmp
tmpfs 16.0M 0 16.0M 0% /var/run
tmpfs 32.0M 0 32.0M 0% /tmp
tmpfs 459.7M 0 459.7M 0% /media/ram
/dev/mapper/store-media
27.5G 64.0K 27.5G 0% /media/internal
lvscan
Code:
ACTIVE '/dev/store/root' [568.00 MB] inherit
ACTIVE '/dev/store/var' [64.00 MB] inherit
ACTIVE '/dev/store/update' [16.00 MB] inherit
ACTIVE '/dev/store/log' [24.00 MB] inherit
ACTIVE '/dev/store/mojodb' [256.00 MB] inherit
ACTIVE '/dev/store/filecache' [136.00 MB] inherit
ACTIVE '/dev/store/media' [27.53 GB] inherit
ACTIVE '/dev/store/swap' [512.00 MB] inherit
fstab
Code:
# fstab auto-generated by trenchcoat
# <filesystem> <mount point> <type> <options> <dump> <pass>
rootfs / ext3 ro,suid,dev,exec,auto,nouser,async,noatime 1
1
/dev/mapper/store-var /var ext3 noatime,data=writeback 0 0
/dev/mapper/store-cryptodb /var/db ext3 noauto,noatime,data=ordered
0 0
/dev/mapper/store-cryptofilecache /var/file-cache ext3 noauto,noatime,u
ser_xattr 0 0
/dev/mapper/store-log /var/log ext3 noatime 0 0
/dev/mapper/store-update /var/lib/update ext3 noauto,noatime 0
0
proc /proc proc defaults 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
tmpfs /tmp tmpfs size=40M,mode=1777 0 0
tmpfs /var/run tmpfs size=16M,mode=1777 0 0
tmpfs /var/tmp tmpfs size=32M,mode=1777 0 0
tmpfs /media/ram tmpfs defaults 0 0
/dev/mapper/store-media /media/internal vfat utf8,shortname=mixed,umask=0000
0 0
===================
Actually fixing it
===================
I found something different using the lvdisplay command verses another thread where a guy posted his.
This is from another forum I found, look at segments
Code:
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID GwzQv1-Oewn-niF3-y2i4-jM23-n8ke-DbWAzV
LV Write Access read/write
LV Status available
# open 1
LV Size 4.00 GB
Current LE 512
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
Here is mine.
Mine for some reason shows 2 segments instead of 1, so I assume there is a problem here.
Code:
---Logicalvolume---
LV Name /dev/store/media
VG Name store
LV UUID muJmcF-yDe4-qF6d-QA8E-T31q-FMSq-6RTiZx
LV Write Access read/write
LV Status available
# open 1
LV Size 27.53GB
Current LE 3524
Segments 2
Allocation inherit
Read ahead sectors auto
-currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
.
[edit1] - I managed to fixed having 2 segments by deleting that partition altogether and making a new one, I assume mine had 2 segments due to me formatting it in windows.
[edit2] - after booting up my touchpad and hooking it up to my computer, I can see all the files on that partition again.
======================================
Edit 2
======================================
Thanks to TheSilverRing for pointing out I forgot to mention how to actually fix it
I fixed the mounting problem by formatting log and var to ext3.
use these commands -
mkfs.ext3 /dev/mapper/store-var
mkfs.ext3 /dev/mapper/store-log
mount -a
mkdir /var/log
mkdir /var/tmp
mkdir /var/run
I doctored my touchpad, and it boots up to live another day.
Hi, I'm having the same error when I try to doctor my TouchPad, although I haven't installed CM7 or messed with my unit in any way, it came with this problem out of the box.
So I try to do the same thing you did, I tried to format the log volume using developer mode console as well as the available console after failed doctoring. Both ways it claims to format successfully, but still gives "Invalid Argument" error when I try to mount the volume. I tried checking the filesystem on the volume, I get an error suggesting "zero size partition", although lvscan says that the log volume is 64MB. I can't remove any volumes or volume group from lvm either, it says it does it but I scan it again and its still there. Basically any changes I try to make are not persistent.
What do I do to fix this?
My touchpad seems to be in read only mode. Not able to webos doctor properly because of it. Cant reinstall cyanogenmod either. I have access to webos recovery and clockwork mod. Any command to get write access back?
hyperfire21 said:
My touchpad seems to be in read only mode. Not able to webos doctor properly because of it. Cant reinstall cyanogenmod either. I have access to webos recovery and clockwork mod. Any command to get write access back?
Click to expand...
Click to collapse
After 5 frustrating evenings alternating between charging and linux shell of the nova boot image trying to wipe partitions and partition table to be able to doctor again, I did not succeed. It simply won't write anything, including the block device of the flash. Because I didn't have cyanogenmod installed or anything other than WebOS, I did not void my warranty, so I sent it to HP, because it would not update or doctor to 3.0.4 . It arrived at the El Paso, TX facility on Friday, should have it (or the replacement) back by the end of the week.
Look in this thread for the outcome, when HP sends me back my TouchPad:
http://forum.xda-developers.com/showthread.php?t=1326004&page=2
I put my touchpad into a similar state, although mine did not end up with the 2 segments. I wiped my partition 14 with dd, sort of deliberately. I was investigating a native openembedded linux build but got wrapped around the axle with the uImage boot cmd line. Anyway, I got tired of using lvm as the kernel cmd line becomes more complex. So when I was putting things back I did the same lvm.static commands and pretty much what the OP did here, I have 2 touchpads so I copied the LVM structure from the golden one, it was the same as listed here.
There are a couple of things that might help someone that were not mentioned -
When booting you may see an error like:
mount: mounting /dev/mapper/store-var on /var failed: Invalid argument
mount: mounting /dev/mapper/store-log on /var/log failed: Invalid argument
What you need to do is format store-var and store-log like the OP said.
However, you will also need to create some mount points in var too, as per the fstab:
mkfs.ext3 /dev/mapper/store-var
mkfs.ext3 /dev/mapper/store-log
mount -a
mkdir /var/log
mkdir /var/tmp
mkdir /var/run
---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------
what do you mean by read-only mode?
mount -o remount, rw /
replace '/' with whatever mount point your want Read/Write, you didn't really make clear what you meant by read-only.
Look at the fstab above, the lines with 'ro' , in them specifically the root, will be mounted read only.
If the file system has errors the os will mount it read only too - fsck the partition to fix it.
Could you post something about the error such as the novaterm command you are trying to execute as well as the output from 'mount'
I will mention my case for the record, my TouchPad had a problem writing to the flash, like the partition table writing failed, formatting filesystems failed, wiring to block device failed with I/O errors.
HP replaced components inside my TouchPad to solve the problem. If you have not voided the warranty on your device and your flash fails to write, you have a hardware problem, and should have HP service it at no cost to you.
Please try all the software repair methods posted in these threads before blaming the hardware though!!!
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
(For 32GB Touchpads 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
Click to expand...
Click to collapse
(16GB Touchpads)
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
Click to expand...
Click to collapse
8) When done, reboot the Touchpad into recovery (Power + Center/Home until screen off, then Power + Volume Up)
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
Branch 1) You can stop here to have 3.0.0 as your webOS version. You've just completed a downgrade that was before thought impossible.
Branch 2) If you want webOS 3.0.4, continue on.
10) When webOS Doctor is complete, hold down Power and Center, and when the screen turns off, immediately hold Power and Volume Up.
11) You'll see the USB icon again, just run webOS Doctor 3.0.4 and you're done.
Have fun.
_____________________________
For those having problems with novaterm:
LordGibson said:
I had the same problem with the downloaded novaterm on three different win7x64 machines. If you've run WebOS Doctor at all you should have a Palm, Inc/terminal/ folder with a novaterm.bat in it. Try using that instead.
Click to expand...
Click to collapse
For those having problems with Java:
lafester said:
got it working by adding the path to java.
set PATH =%PATH%;c:\program files (x86)\java\jre6\bin.
Click to expand...
Click to collapse
If someone can, can they provide the partition layout for 16GB Touchpads?
How could we find the partition layout ?
Edit :
--
I ran the following command on my 16GB TouchPad :
Code:
lvm.static vgdisplay
And I get :
Code:
Free PE / Size 1683 / 13.15 GB
Is it what you're looking for ?
spadewalk said:
How could we find the partition layout ?
Edit :
--
I ran the following command on my 16GB TouchPad :
Code:
lvm.static vgdisplay
And I get :
Code:
Free PE / Size 1683 / 13.15 GB
Is it what you're looking for ?
Click to expand...
Click to collapse
Can you run lvm.static lvdisplay ?
Sure.
Here you have :
Code:
lvm.static lvdisplay
--- Logical volume ---
LV Name /dev/store/root
VG Name store
LV UUID Aq5Mpj-p1ou-AMwd-j0YJ-1ytK-nHVn-NlOGUR
LV Write Access read/write
LV Status available
# open 1
LV Size 568.00 MB
Current LE 71
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 0
Block device 254:0
--- Logical volume ---
LV Name /dev/store/var
VG Name store
LV UUID 1OQAZu-Zx0P-fK6M-xdYj-8T0z-CoDw-2pwy00
LV Write Access read/write
LV Status available
# open 1
LV Size 64.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 1
Block device 254:1
--- Logical volume ---
LV Name /dev/store/update
VG Name store
LV UUID 9Cpv99-Al2S-eCWp-ioAi-AGMS-T10i-qba3pn
LV Write Access read/write
LV Status available
# open 0
LV Size 16.00 MB
Current LE 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 2
Block device 254:2
--- Logical volume ---
LV Name /dev/store/log
VG Name store
LV UUID jaNcqX-uRU7-uwWi-yvZE-KHiN-K5RX-mh3jkJ
LV Write Access read/write
LV Status available
# open 1
LV Size 24.00 MB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 3
Block device 254:3
--- Logical volume ---
LV Name /dev/store/mojodb
VG Name store
LV UUID 7nT2OX-nlbV-U6HQ-UrVi-Pja6-nDwP-BpHsTR
LV Write Access read/write
LV Status available
# open 1
LV Size 256.00 MB
Current LE 32
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 4
Block device 254:4
--- Logical volume ---
LV Name /dev/store/filecache
VG Name store
LV UUID oH0jt0-AcIO-pFTF-3wD7-cYC2-W88I-H0UqPj
LV Write Access read/write
LV Status available
# open 1
LV Size 136.00 MB
Current LE 17
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 5
Block device 254:5
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID NWNspe-aKe5-glCM-c0mb-15sM-32Mu-64e8jx
LV Write Access read/write
LV Status available
# open 1
LV Size 12.64 GB
Current LE 1618
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
--- Logical volume ---
LV Name /dev/store/swap
VG Name store
LV UUID TOq7Y8-2XCB-diKE-3D7s-3pIp-Ksbl-4LbZP0
LV Write Access read/write
LV Status available
# open 1
LV Size 512.00 MB
Current LE 64
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 7
Block device 254:7
spadewalk said:
Sure.
Here you have :
Code:
lvm.static lvdisplay
--- Logical volume ---
LV Name /dev/store/root
VG Name store
LV UUID Aq5Mpj-p1ou-AMwd-j0YJ-1ytK-nHVn-NlOGUR
LV Write Access read/write
LV Status available
# open 1
LV Size 568.00 MB
Current LE 71
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 0
Block device 254:0
--- Logical volume ---
LV Name /dev/store/var
VG Name store
LV UUID 1OQAZu-Zx0P-fK6M-xdYj-8T0z-CoDw-2pwy00
LV Write Access read/write
LV Status available
# open 1
LV Size 64.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 1
Block device 254:1
--- Logical volume ---
LV Name /dev/store/update
VG Name store
LV UUID 9Cpv99-Al2S-eCWp-ioAi-AGMS-T10i-qba3pn
LV Write Access read/write
LV Status available
# open 0
LV Size 16.00 MB
Current LE 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 2
Block device 254:2
--- Logical volume ---
LV Name /dev/store/log
VG Name store
LV UUID jaNcqX-uRU7-uwWi-yvZE-KHiN-K5RX-mh3jkJ
LV Write Access read/write
LV Status available
# open 1
LV Size 24.00 MB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 3
Block device 254:3
--- Logical volume ---
LV Name /dev/store/mojodb
VG Name store
LV UUID 7nT2OX-nlbV-U6HQ-UrVi-Pja6-nDwP-BpHsTR
LV Write Access read/write
LV Status available
# open 1
LV Size 256.00 MB
Current LE 32
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 4
Block device 254:4
--- Logical volume ---
LV Name /dev/store/filecache
VG Name store
LV UUID oH0jt0-AcIO-pFTF-3wD7-cYC2-W88I-H0UqPj
LV Write Access read/write
LV Status available
# open 1
LV Size 136.00 MB
Current LE 17
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 5
Block device 254:5
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID NWNspe-aKe5-glCM-c0mb-15sM-32Mu-64e8jx
LV Write Access read/write
LV Status available
# open 1
LV Size 12.64 GB
Current LE 1618
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
--- Logical volume ---
LV Name /dev/store/swap
VG Name store
LV UUID TOq7Y8-2XCB-diKE-3D7s-3pIp-Ksbl-4LbZP0
LV Write Access read/write
LV Status available
# open 1
LV Size 512.00 MB
Current LE 64
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 7
Block device 254:7
Click to expand...
Click to collapse
Thank you. I was able to make the correct commands for 16GB Touchpads.
Good, that's awesome.
where is the novacom installer?
and the webdoctor, for that matter?
did i have to read 20 other threads / posts before this one?
lol
serialteg said:
where is the novacom installer?
and the webdoctor, for that matter?
did i have to read 20 other threads / posts before this one?
lol
Click to expand...
Click to collapse
If you even bothered to look at the post, you'd see that next to each one, there is a word that says "click". And if you clicked on them, you'd see that they are DIRECT links to what you need.
Just wanted to say this worked for me too; in case anyone is worried. I had Ubuntu native, CM9, and Webos (duh) installed but my /media/internal partition was messed up (webos and windows 7 said it was 22GB while lvscan said 14GB). I tried doctoring but just got a hp logo boot loop. These commands got me back to webos.
same here, but after following this tutorial my touchpad iz back to life, thank you !
Wow this is a great tut and I bet there is a lot of people who wI'll
Be needing this soon!!
Thanks
saved my TP thanks!!! but my app catalog has a yellow triangle in the corner....any ideas?
Sadly, this did not work for me. The WebOS Doctor 3.0.0 completes successfully but the TP never boots up fully - rolls right back into the boot loop. Just for the hell of it I ran the 3.0.5 update afterwards. That also completes successfully, but lands right back into the boot loop.
I've just finished my third attempt from start to finish with no luck. Guess I must be looking at a hardware problem. . . Any other ideas?
LordGibson said:
Sadly, this did not work for me. The WebOS Doctor 3.0.0 completes successfully but the TP never boots up fully - rolls right back into the boot loop. Just for the hell of it I ran the 3.0.5 update afterwards. That also completes successfully, but lands right back into the boot loop.
I've just finished my third attempt from start to finish with no luck. Guess I must be looking at a hardware problem. . . Any other ideas?
Click to expand...
Click to collapse
Did you run the comands in order and did you use the proper partition setup for your touchpad?
rr5678 said:
Did you run the comands in order and did you use the proper partition setup for your touchpad?
Click to expand...
Click to collapse
Affirmative. By the third time through I was pretty anal about doing everything perfectly and exactly as indicated.
LordGibson said:
Affirmative. By the third time through I was pretty anal about doing everything perfectly and exactly as indicated.
Click to expand...
Click to collapse
Start it. And while it's doing the boot loop, see if you can connect with novaterm.
It's a refurb unit, so it's probably a hardware problem - just strange that the doctors seemingly work so well.
Maybe I'll try 16gb just for the hell of it. Perhaps it was mis-labeled. . .
---------- Post added at 10:27 PM ---------- Previous post was at 10:23 PM ----------
rr5678 said:
Start it. And while it's doing the boot loop, see if you can connect with novaterm.
Click to expand...
Click to collapse
No joy. Windows signals a connection, but can't find device in novaterm.
---------- Post added at 10:54 PM ---------- Previous post was at 10:27 PM ----------
LordGibson said:
Maybe I'll try 16gb just for the hell of it. Perhaps it was mis-labeled. . .
Click to expand...
Click to collapse
For future reference, I would recommend against this course of action.
LordGibson said:
---------- Post added at 10:27 PM ---------- Previous post was at 10:23 PM ----------
No joy. Windows signals a connection, but can't find device in novaterm.
Click to expand...
Click to collapse
Boot it into the recovery uImage and check what's in the boot folder.
LordGibson said:
---------- Post added at 10:54 PM ---------- Previous post was at 10:27 PM ----------
For future reference, I would recommend against this course of action.
Click to expand...
Click to collapse
You could have had yourself a doorstop.
Code:
[email protected]:/boot# ls -la
drwxr-xr-x 2 root root 1024 Jul 30 2011 .
drwxr-xr-x 17 root root 1024 Jul 30 2011 ..
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
lrwxrwxrwx 1 root root 29 Jul 30 2011 uImage -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
hey everyone, yes im abit of a noob and need some help.
i was trying to install Arch on my touchpad and hit an error. now my touchpad keeps cycling the hp logo and wont turn on or off. ive tried webos doctor and still this problem is still here.
please help
thank you for any help given
give us some details on how did it occur and what were you doing when it gave you an error (what was the last command you run for example)
"curl -O http://archlinuxarm.org/mirror/touchpad/ArchLinuxARM-touchpad-latest.tar.gz"
this was the last command i wrote, and it downloaded about 39mb and failed. before this i had partitioned the hard drive too.
is this fixable?
sissons87 said:
before this i had partitioned the hard drive too.
Click to expand...
Click to collapse
i think the keyword for the problem is here, can you recall what commands exactly did you run?
also just like chessmaster w/nook asked you, do you have moboot installed?
Holding down the power and home key always reset my tp. And with HP its pretty impossible to brick ur device HP doc
okay heres a detailed explanation of what i done.
i put my touchpad in to dev mode.
accessed novaterm from my ubuntu window.
i then followed all of these commands:
"mount -o rw,remount /boot
cd /tmp
curl -O http://moboot.googlecode.com/files/moboot_0.3.5.zip
unzip moboot_0.3.5.zip
mv uImage.moboot_0.3.5 /boot/uImage.moboot
cd /boot
rm uImage
ln -s uImage.moboot uImage
ln -s uImage-2.6.35-palm-tenderloin uImage.webOS
echo "yes" > moboot.verbose.ArchLinuxARM
sync
curl -O http://archlinuxarm.org/mirror/touchpad/uImage.ArchLinuxARM
curl -O http://archlinuxarm.org/mirror/touchpad/moboot.splash.ArchLinuxARM.tga
cd /tmp
pkill -SIGUSR1 cryptofs
umount /media/internal
echo "STOP HERE AND READ 'RESIZE FAT' BEFORE CONTINUING" # See below
resizefat /dev/store/media ****M
lvm.static lvresize -L -4096M /dev/store/media
lvm.static lvcreate -L 4096M -n arch-root store
mkfs.ext3 /dev/store/arch-root
mkdir linux
mount /dev/store/arch-root linux
cd linux
curl -O http://archlinuxarm.org/mirror/touchpad/ArchLinuxARM-touchpad-latest.tar.gz
tar xzf ArchLinuxARM-touchpad-latest.tar.gz # Will take a long time
rm ArchLinuxARM-touchpad-latest.tar.gz
cd ..
umount linux
reboot # The first few times, this may error out - try again"
where the ****M is i put 7944M i think this may be the issue.
when i got to this command it started downloading and then got an error at 39mb:
"curl -O http://archlinuxarm.org/mirror/touchpad/ArchLinuxARM-touchpad-latest.tar.gz"
ive then ran webos doctor numbers of times but no luck. it wont even let me novaterm back in not sure what to do :/ any help would be great.
sissons87 said:
hey everyone, yes im abit of a noob and need some help.
i was trying to install Arch on my touchpad and hit an error. now my touchpad keeps cycling the hp logo and wont turn on or off. ive tried webos doctor and still this problem is still here.
please help
thank you for any help given
Click to expand...
Click to collapse
I had that same bootloop problem. Try this: http://forum.xda-developers.com/showthread.php?t=1426244
rr5678 said:
I had that same bootloop problem. Try this: http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
All has worked okay but having problems creating swap store. Error im getting is:
Redundant stripes arguement: default is 1
Insufficiant free extents (0) in volume group store: 64 required
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
sissons87 said:
All has worked okay but having problems creating swap store. Error im getting is:
Redundant stripes arguement: default is 1
Insufficiant free extents (0) in volume group store: 64 required
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Did you enter
"lvm.static lvcreate -l 1761 -i 1 -M y --major 254 --minor 6 -n media store"
or
"lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store"?
rr5678 said:
Did you enter
"lvm.static lvcreate -l 1761 -i 1 -M y --major 254 --minor 6 -n media store"
or
"lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store"?
Click to expand...
Click to collapse
I entered " "lvm.static lvcreate -l 1648 -i 1 -M y --major 254 --minor 6 -n media store" i wouldnt let me put 1761 cus i got the same sort of error.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
sissons87 said:
I entered " "lvm.static lvcreate -l 1648 -i 1 -M y --major 254 --minor 6 -n media store" i wouldnt let me put 1761 cus i got the same sort of error.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Okay, try it again, except this time, enter
"lvm.static lvcreate -l 1584 -i 1 -M y --major 254 --minor 6 -n media store"
Okay how do i undo what ive just done? Run all commands again?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
sissons87 said:
Okay how do i undo what ive just done? Run all commands again?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Yes, running them again will erase all the necessary stuff so you can rebuild it.
Okay thank you, i will try that now
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Hii !
I got exactly the same problem ! And I followed a tutorial I found on rootzwiki (dumb I can't post the link cuz this is my first message).
Anyway look for that on Google (with the quotes) :"HOW TO make a larger cm7 data partition" touchpad
It's a txt file and it worked all fine on mine. Hope it would help you.
would like to thank you all for all your help rr5678 you were a great help! im going to and try install arch again or another os now. wish me luck dnt learn with out try eh
Thanks a lot rr5678 too for your tutorial, I figured that the tutorial I found wasn't good as yours.
sissons87 said:
would like to thank you all for all your help rr5678 you were a great help! im going to and try install arch again or another os now. wish me luck dnt learn with out try eh
Click to expand...
Click to collapse
Glad to hear that it worked for you.
Flash files are available here to automatically create the swap partition:
https://forum.xda-developers.com/hp-touchpad/general/how-to-create-swap-partition-size-t3892060#post78939182
How to configure the Hp Touchpad internal storage
The most important feature that was ahead of its time and still until today is the use of LVM (Logical Volume Manager) for managing the internal storage.
To the regular user it will be insignificant but it can provide great benefits if deploy properly.
I could be wrong, but the TP could be the first and only mobile device ever shipped with LVM even now. (someone can correct me on this)
What is LVM?
https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)
I am a regular user and not an expert on LVM in Linux, the only device that I have to play with LVM is the TP and will show you the basics usage and it may not even have the full potential settings.
In webOS there is a program (app) call Tailor ( Formerly Known as Resizah ), a graphical interface to manage LVM.
http://preware.pivotce.com/package/org.webosinternals.tailor
https://www.webos-internals.org/wiki/Application:Tailor
https://forums.webosnation.com/webos-internals/304871-tailor-device-live-partition-filesystem-editor-beta-testing.html
https://github.com/rwhitby/tailor
The last alpha version 0.3.1 allows for creating a LuneOS partition.
Also you can create all Android partitions inside WebOS, create and resize all partitions while running WebOS.The magic of LVM!
Attached is a screen shot of my TP running Taylor.
Think of it as creating, deleting , moving, expanding or reducing (files and folders) with your file manager. Instead it will be the actual storage card, partitions, volumes. All done withing the OS no need to reboot or enter any commands. Resizing the android system, cache or data partition live inside android with just touch input.! That is how easy it could have been, but Android does not use LVM and the TP had to follow the rest of the herd. The reason that WebOS, Android, LuneOS (and more OS) can be install together is due to the flexibility of LVM.
The ToolBox by jcsullins provides scripts to create webOS and Android volumes and resize system, cache and data. But is not a live system and limited to pre-configure settings.
All the flexibility and easy to use comes with a risk of data lost as we know not everything in the computer world works as intended, due to the endless configuration and uses of each user.
Code:
This is a 32G Touchpad with WebOS, Android and LuneOS install and perfectly running.
Factory install WebOS (original)
Used ToolBox to create Android system, cache and data
Used Taylor to create luneos-root
List of physical volumes
/dev/store/root [ 568.00 MB]
/dev/store/var [ 64.00 MB]
/dev/store/update [ 16.00 MB]
/dev/store/log [ 24.00 MB]
/dev/store/mojodb [ 256.00 MB]
/dev/store/filecache [ 136.00 MB]
/dev/store/media [ 19.44 GB]
/dev/store/swap [ 400.00 MB]
/dev/store/cm-cache [ 200.00 MB]
/dev/store/cm-data [ 4.88 GB]
/dev/store/cm-system [ 1.17 GB]
/dev/store/luneos-root [ 1.95 GB]
12 disks
0 partitions
0 LVM physical volume whole disks
0 LVM physical volumes
LVM is reporting to each OS its own disks and each OS mounts its own Disk using f stabs. In reality there is only one storage, not 12 ( the magic of LVM !
This is a 32G Touchpad that was completely reset using the Toolbox.
/dev/block/mmcblk0p8 [ 10.00 MiB]
/dev/block/mmcblk0p9 [ 1.46 MiB]
/dev/block/mmcblk0p1 [ 100.00 MiB]
/dev/block/mmcblk0p10 [ 3.00 MiB]
/dev/block/mmcblk0p11 [ 3.00 MiB]
/dev/block/mmcblk0p3 [ 1.46 MiB]
/dev/block/mmcblk0p12 [ 4.00 MiB]
/dev/block/mmcblk0p13 [ 32.00 MiB]
/dev/block/mmcblk0p14 [ 29.09 GiB] LVM physical volume
/dev/block/mmcblk0p6 [ 750.00 KiB]
/dev/store/media [ 29.09 GiB]
/dev/block/mmcblk0p7 [ 2.44 MiB]
1 disk
10 partitions
0 LVM physical volume whole disks
1 LVM physical volume
/dev/block/mmcblk0p13 ( is the boot partition ) 32 MB where all the uImages are boot it from.
This is the physical volume the real internal storage.
PV VG Fmt Attr PSize PFree
/dev/block/mmcblk0p14 store lvm2 a- 29.09g 0
This is the logical volume of the physical volume which is part of the volume group "store"
The media USB storage in Android. This is the logical volume to resize and create other logical volume.
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID WhFWig-xwTY-0SK3-OnrS-32mq-gADG-7mLY7c
LV Write Access read/write
LV Status available
# open 1
LV Size 29.09 GiB
Current LE 3723
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 4096
Persistent major 254
Persistent minor 6
Block device 253:6
This is all done loading TWRP mounting /boot and adb shell.
The working directory for lvm.static is:
/boot/usr/sbin
to execute ./lvm.static plus command.
Resizing Logical volume /dev/store/media to 1GB
./lvm.static lvresize --size 1G /dev/store/media
PV VG Fmt Attr PSize PFree
/dev/block/mmcblk0p14 store lvm2 a- 29.09g 28.09g
Now there is 28.09g free to be allocated to any volume (disk) we want to create
Keep in mind the Persistent minor is 6 of the major 254 ( the next disk can be from 0 to 5 and 7 to 254 ) but 6 is already taken.
Creating Android volume cm-system
./lvm.static lvcreate -L 1.3G -M y --major 254 --minor 0 -n /dev/store/cm-system
Creating Android volume cm-cache
./lvm.static lvcreate -L 200M -M y --major 254 --minor 1 -n /dev/store/cm-cache
Creating Android volume cm-data (4GB)
./lvm.static lvcreate -L 4G -M y --major 254 --minor 2 -n /dev/store/cm-data
Activating the new logical volume
/boot/usr/sbin # ./lvm.static vgchange -ay
4 logical volume(s) in volume group "store" now active
/boot/usr/sbin # ./lvm.static pvs
PV VG Fmt Attr PSize PFree
/dev/block/mmcblk0p14 store lvm2 a- 29.09g 22.59g
There is 22.59GB free to create more volume or disk!
Let's create volumes to install Linux as chroot
./lvm.static lvcreate -L 2G -M y --major 254 --minor 5 -n /dev/store/Linux-root
Another chroot as Debian!
./lvm.static lvcreate -L 2G -M y --major 254 --minor 7 -n /dev/store/debian-root
Create LuneOS volume
./lvm.static lvcreate -L 2G -M y --major 254 --minor 4 -n /dev/store/luneos-root
There is 16.59GB free
/boot/usr/sbin # ./lvm.static pvs
PV VG Fmt Attr PSize PFree
/dev/block/mmcblk0p14 store lvm2 a- 29.09g 16.59g
Let's create another Android installation ( completely independent )
Android PIE system
./lvm.static lvcreate -L 1.3G -M y --major 254 --minor 8 -n /dev/store/A_PIE-system
Android PIE cache
./lvm.static lvcreate -L 200M -M y --major 254 --minor 9 -n /dev/store/A_PIE-cache
Android PIE Data (4GB)
./lvm.static lvcreate -L 4G -M y --major 254 --minor 10 -n /dev/store/A_PIE-data
There is 11.09GB free
/boot/usr/sbin # ./lvm.static pvs
PV VG Fmt Attr PSize PFree
/dev/block/mmcblk0p14 store lvm2 a- 29.09g 11.09g
Let's create SailFishOS!
./lvm.static lvcreate -L 2G -M y --major 254 --minor 11 -n /dev/store/Sailfish_OS
Another Installation Android 10 Queso!
A_Queso-system
./lvm.static lvcreate -L 1.3G -M y --major 254 --minor 12 -n /dev/store/A_Queso-system
A_Queso-cache
./lvm.static lvcreate -L 200M -M y --major 254 --minor 13 -n /dev/store/A_Queso-cache
A_Queso_data
./lvm.static lvcreate -L 2G -M y --major 254 --minor 14 -n /dev/store/A_Queso_data
There is 5.59GB free
PV VG Fmt Attr PSize PFree
/dev/block/mmcblk0p14 store lvm2 a- 29.09g 5.59g
What about a swap volume!
./lvm.static lvcreate -L 1G -C y -M y --major 254 --minor 15 -n /dev/store/swap
Now we can give the command to LVM to extend media to use the 4.59GB available and use it all.
/lvm.static lvresize -l 100%FREE /dev/store/media
15 logical volume(s) in volume group "store" now active
Here is the summary of all the disks available:
/boot/usr/sbin # ./lvm.static lvmdiskscan
/dev/block/mmcblk0p8 [ 10.00 MiB]
/dev/store/cm-system [ 1.30 GiB]
/dev/block/mmcblk0p9 [ 1.46 MiB]
/dev/block/mmcblk0p1 [ 100.00 MiB]
/dev/store/cm-cache [ 200.00 MiB]
/dev/block/mmcblk0p10 [ 3.00 MiB]
/dev/store/cm-data [ 4.00 GiB]
/dev/block/mmcblk0p11 [ 3.00 MiB]
/dev/block/mmcblk0p3 [ 1.46 MiB]
/dev/block/mmcblk0p12 [ 4.00 MiB]
/dev/store/luneos-root [ 2.00 GiB]
/dev/block/mmcblk0p13 [ 32.00 MiB]
/dev/store/Linux-root [ 2.00 GiB]
/dev/block/mmcblk0p14 [ 29.09 GiB] LVM physical volume
/dev/block/mmcblk0p6 [ 750.00 KiB]
/dev/store/media [ 4.59 GiB]
/dev/block/mmcblk0p7 [ 2.44 MiB]
/dev/store/debian-root [ 2.00 GiB]
/dev/store/A_PIE-system [ 1.30 GiB]
/dev/store/A_PIE-cache [ 200.00 MiB]
/dev/store/A_PIE-data [ 4.00 GiB]
/dev/store/Sailfish_OS [ 2.00 GiB]
/dev/store/A_Queso-system [ 1.30 GiB]
/dev/store/A_Queso-cache [ 200.00 MiB]
/dev/store/A_Queso_data [ 2.00 GiB]
/dev/store/swap [ 1.00 GiB]
15 disks
10 partitions
0 LVM physical volume whole disks
1 LVM physical volume
Now we can format every disk with ext2, ext3, ext4 and vfat
Example to format Android system volumen
mke2fs -E lazy_itable_init=0 -t ext4 /dev/store/cm-system
mke2fs -E lazy_itable_init=0 -t ext4 /dev/store/cm-cache
mke2fs -E lazy_itable_init=0 -t ext4 /dev/store/cm-data
To make swap
mkswap /dev/store/swap
This is very easy to create, and quick there is no waitting time is done as soon as you press enter.
We have create it a Touchpad that is capable of running the following OS independently.
Current Version of Android
A version of Android PIE 9
A version of Android Queso 10
LuneOS
SailfishOS
Linux-root (to run as chroot or native)
debian-root (to run as chroot or native)
A 1GB swap file
The volume size of the disk created are minimum or below requirement but this is to show how powerful and simple LVM is to set up.
Hi @HP_TOUCHPAD !
Good to see someone with your structured approach sharing tutorials and hints! Cheers for that!
I stumbled upon my 16GB and 32GB Touchpads on the weekend and I want to give them a new spin.
Especially LuneOS was not known to me before your post!
Any chance of you sharing your current setup and how you managed to set it up?
I am curious to factory reset my Touchpads (at least the 32GB one) and set them up with webOS + LuneOS + Android (which ROM do you use?)...
You being the knowledgable 'tutor' around here - would you share your 'webOS + LuneOS + Android' experience and how to set it up?
Cheers!
Curious greetings, raimerik
Thank you for your comments!
As of right now I am working on just that, a simple way for anyone just to flash a zip file and have everything that you need to have the Tablet set up. There is a lot of steps to do and gets confusing, hopefully the new process will work for everyone.
I will post when done!
HP_TOUCHPAD said:
Thank you for your comments!
As of right now I am working on just that, a simple way for anyone just to flash a zip file and have everything that you need to have the Tablet set up. There is a lot of steps to do and gets confusing, hopefully the new process will work for everyone.
I will post when done!
Click to expand...
Click to collapse
Wow - cheers! - looking forward to testing it once it's done! :] raimerik
I will try it and test it out too. My Touchpad is afraid of nothing.
Let's face it, these tablets have had a good run but they're just unusably slow and laggy with any remotely modern version of android. Unfortunately going back to stock is not the simplest in 2022, especially if you've tried one of the more extreme android installs which wipes WebOS and rebuilds the partition table. I spent the morning collecting files and putting together a process from about 25 different websites dating back to 2012. The most comprehensive guide I found was Here but it still didn't fully work for me and some commands had to be done differently, particularly when rebuilding the partitions.
Keep in mind I wasn't kidding when I called this the nuclear option. If you can use any other less extreme method you probably should. This one is a risky pain and basically boils down to nuking the whole thing from orbit before rebuilding the partitions line by line by hand in a terminal.
Necessary files
Everything can be found in this mega folder
ACMEUninstaller2
Novacom
devicetool.jar
WebOS doctor jars (versions 3.0.0 and 3.0.5 in conjunction with devicetool should let you skip the now broken WebOS activation step)
7zip or similar program that can open jar files
Recovery image (nova-installer-image-topaz.uimage)
Java
WebOS quick install
Setup
Make sure Java is installed and working on your system
Make sure your touchpad is fully charged
Open Novacom files.zip and find the right version for your architecture. Odds are that's win-64. If you're on linux check your distro's repos first
Reboot (esp if you're on windows)
Find the Palm, Inc (lowercase L, capital i) folder. On windows this defaults to c:/Program Files/Palm, Inc
Place nova-installer-image-topaz.uimage in your Palm, Inc folder
Place ACMEUninstaller2 in your Palm, Inc folder
Boot your touchpad into WebOS recovery mode, either via bootloader or by holding power+volumeup (can take up to ~30secs)
Open a terminal window and navigate to your Palm, Inc folder
Run one of the below commands. THIS IS THE POINT OF NO RETURN.
Windows: novacom.exe boot mem:// < ACMEUninstaller2
Mac: ./novacom boot mem:// < ACMEUninstaller2
You should see a bunch of text scrolling and two images of a penguin around the top to one side. When it's finished it will warn you there's nothing installed it recognizes.
Try to reboot into recovery mode. You will probably get an exclamation mark with www.palm.com/ROM below it, or just the HP logo
In the Palm, Incterminal execute the below command (capitalization matters):
novacom boot mem:// < nova-installer-image-topaz.uimage
Navigate your terminal to the terminal subfolder and execute novaterm.bat
A small java window named "NovaTerm:" should pop up on your screen
In the NovaTerm: window click file and then connect
Another popup should appear titled Select device to connect with a really long string of letters and numbers ending in (usb, topaz-linux) in it. Click OK
If not check the dropdown arrow, make sure your USB is connected, reboot if all else fails and try again
Now that NovaTerm:says it's connected go back to your terminal and execute the below:
Windows: novacom -t open tty://
Everything else: novaterm should have been enough
Your terminal should now say [email protected]:/# or the like. There may be some extra gibberish if you pressed an arrow key or something.
Now you need to rebuild all your partitions. Execute ONE of the code blocks below these instructions in exact order, one line at a time. You should not see any errors about something being mounted or the like. If you do reboot your touchpad and try to restart from step 13, that's what I did.
Once that is done try to reboot into recovery mode again, you'll probably only get the HP logo instead of the big USB symbol.
Open a new terminal window and navigate to wherever you're keeping the WebOS Doctor jar files
start WebOS doctor 3.0.0 (the only version that can deal with partition issues) from inside the terminal so you can see the output: java -jar webosdoctorp300hstnhwifi_customhpactivationbypass.jar
Don't touch the WebOS doctor window. Moving it to other monitors seems to break it for some reason.
If you see errors where it's trying to find the device and can't try unplugging/replugging the touchpad. If that doesn't work try rebooting. One person said uninstalling novacom at this point and letting WebOS reinstall the drivers fixed it. It seems hit or miss if there's weird USB detection issues on Win10.
WebOS doctor should complete without issues and have you reboot.
When the touchpad successfully reboots it'll ask start asking you for a language and first time activation. HP's master servers are down, this won't work. Reboot into recovery again
Navigate your terminal to wherever you're keeping devicetool.jar and execute it: java -jar path/to/devicetool.jar
Your terminal should say "found device: topaz-bootie" and then talk about configuring things and volumes for a while.
Once the terminal says Device is ready. reboot once final time.
That should be it. Once you've got everything installed and WebOS up and running there's still a few steps needed to deal with the lack of auth servers and expired certificates.
Enable developer mode by putting webos20090606 into the "Just Type" bar on the homepage and hitting enter
Run WebOS-Quick-Install-4-7-2.jar just as if it were a normal application (no need for terminal). It's basically a replacement app store that runs on the PC.
You should see the HP Touchpad recognized by WebOs Quick Install. If it is click the globe on the right side of the app's window
Search for "Preware" in the popup (you need to click the magnifying glass after typing)
Install Preware, which is a replacement app store that runs on the touchpad itself
32gb touchpad partitions
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
16gb touchpad partitions
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 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
Troubleshooting
If your touchpad's home button has an LED blinking from side to side the battery isn't charged enough. Use the stock charger if available and leave it until it boots itself up. This could potentially take days. Mine only took about 12 hours.
If instead of recovery mode you get either a plain HP logo or an exclamation mark with www.palm.com/ROM below it this means your disk is wiped and there isn't even a recovery or anything. You'll need to use novacom to force nova-installer-image-topaz.uimage onto the touchpad and then connect to it externally using the novaterm utility. Once you run ACMEUninstaller2 this is the expected result.
If you're getting errors about the exclusivity of mmcblk0p14 and asking if it's mounted something went weird while running all of the partitions, try rebooting and starting again.
If you want to download the original WebOS doctor files you need to edit your hosts file and add 195.22.200.42 downloads.help.palm.com
A list of all the resources I used to compile this:
https://hroy.eu/tips/webos-touchpad-restore/ (massive credit to Hroy here, this is by far the most complete guide though it still needed tweaks to the partition rebuilding commands)
Code:
https://www.webos-internals.org/wiki/WebOS_Doctor_Versions
https://forum.xda-developers.com/t/q-touchpad-seems-bricked.1971859/page-2#post-57616293
https://www.webos-internals.org/wiki/How_To_Recover#Doctor_disconnects_at_8.25
https://www.webosarchive.org/docs/activate/
https://forums.webosnation.com/hp-touchpad/330977-how-restore-hp-touchpad.html
https://pivotce.com/2015/06/24/tip-how-to-bypass-activation/
https://pivotce.com/2015/12/13/the-ultimate-bypass-activation-tool/
https://forums.webosnation.com/hp-touchpad/329655-hp-tp-server-error.html
https://forums.webosnation.com/hp-touchpad/317164-activation-bypass-touchpad.html
https://forum.xda-developers.com/t/need-help-webos-fails-at-8-for-hp-tp-due-to-insufficient-free-extents-0-in-volume.3275076/
https://forum.xda-developers.com/t/solved-bricked-and-webos-doctor-wont-help.1564938/
https://forums.webosnation.com/hp-touchpad/325404-recurring-maps-download-failed-error-2.html
https://forum.xda-developers.com/t/guide-factory-condition-restoration-downgrade-to-webos-3-0-0.1426244/
https://forums.webosnation.com/hp-touchpad/332616-getting-restarted-touchpad.html
https://forums.webosnation.com/canuck-coding/274461-webos-quick-install-v4-6-0-a.html
https://forum.xda-developers.com/t/tools-touchpad-toolbox-updated-2015-02-25.2756314/page-4#post-52922166
[MEDIA=youtube]VP-FH6fS2GI[/MEDIA]
[MEDIA=youtube]wFAIJiS8g4o[/MEDIA]
https://forum.xda-developers.com/t/rom-guide-how-to-install-android-on-the-hp-touchpad-the-easy-way.2147284/#post-37965549
https://forums.webosnation.com/hp-touchpad/309309-hp-touchpad-booting-issues.html
https://www.rootzwiki.com/threads/the-official-fix-your-touchpad-8-12-stopped-no-sd-opps-reformat-crap-thread.14249/
https://forum.xda-developers.com/t/guide-video-how-to-bypass-webos-activation-on-the-hp-touchpad.3636750/
https://pivotce.com/2015/06/15/tip-edit-your-hosts-file-for-access-to-old-palm-servers/
hi thanks for the guide,
I agree with you android roms lag quite.
Tired too I restored webOs ,having many of your problems, but unfortunately it is a dead operating system.
Despite the fluidity there is no way to use it. I will go back to android testing all the roms.
Unfortunately this tablet is of its age