[Q] Deleting partitions - TouchPad Q&A, Help & Troubleshooting
Recently I flashed AOKP to my TouchPad. This was after I installed an earlier version of CM7. I really want to delete the CM7 off the tablet and just have WebOS and AOKP on the tablet. Is there a way to delete the CM7 partition? I've searched this forum but couldn't find an answer.
I also have a really old bootloader. Are theyre any updated ones?
Thanks in advance.
hope this helps do this at your own risk
do this at your own risk
You need a way to access the WebOS Linux terminal, so we can remove them.
download Novaterm, and launch that from your desktop PC. Alternatively you can use Xecutah local Linux terminal to run the commands below
i use noverterm my self just the way i like it not anyother reason i have done this both ways and it worked for me do this at your own risk
Check and remove partitions
Once you have a terminal open type lvm lvscan and press Return. This will list all of the existing partitions on the HP TouchPad, the three we’re interested in are:
/dev/store/cm-system [304 MB]
/dev/store/cm-cache [200 MB]
/dev/store/cm-data [1.50 GB]
To remove each one type the following lines and press Return after each one:
lvremove /dev/store/cm-system
lvremove /dev/store/cm-cache
lvremove /dev/store/cm-data
back up your HP TouchPad, go to Settings > Backup and click Back Up Now. Once that done, restart the HP TouchPad and as it first powers up hold the Up Volume button and you should see the white USB logo. Connect the TouchPad to your desktop PC. make sure you have webdoctor for your hp touchpad
connected to pc start WebOS Doctor
Youll require Java installed and your HP WebOS account details, plus the device needs at least five percent charge. The entire reset process shouldt take more than half an hour.
now reinstall cm android wish ever version you want again
---------- Post added at 08:18 PM ---------- Previous post was at 07:21 PM ----------
netkillercat said:
do this at your own risk
You need a way to access the WebOS Linux terminal, so we can remove them.
download Novaterm, and launch that from your desktop PC. Alternatively you can use Xecutah local Linux terminal to run the commands below
i use noverterm my self just the way i like it not anyother reason i have done this both ways and it worked for me do this at your own risk
Check and remove partitions
Once you have a terminal open type lvm lvscan and press Return. This will list all of the existing partitions on the HP TouchPad, the three we’re interested in are:
/dev/store/cm-system [304 MB]
/dev/store/cm-cache [200 MB]
/dev/store/cm-data [1.50 GB]
To remove each one type the following lines and press Return after each one:
lvremove /dev/store/cm-system
lvremove /dev/store/cm-cache
lvremove /dev/store/cm-data
back up your HP TouchPad, go to Settings > Backup and click Back Up Now. Once that done, restart the HP TouchPad and as it first powers up hold the Up Volume button and you should see the white USB logo. Connect the TouchPad to your desktop PC. make sure you have webdoctor for your hp touchpad
connected to pc start WebOS Doctor
Youll require Java installed and your HP WebOS account details, plus the device needs at least five percent charge. The entire reset process shouldt take more than half an hour.
now reinstall cm android wish ever version you want again
Click to expand...
Click to collapse
Factory condition restoration Downgrade to webOS 3.0.0 and get back to 3.0.4
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
My pad is 32GB
(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
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.
just in case things go wacky.
I though android just used the same partitions.
Do you mean the moboot entry? The above procedure us the cure all, fix anything, last resort procedure. If you just mean when you boot up you see CM7 and AOKP that is normal, and they point to the same thing generally. Usually both selections will boot whatever was installed last. If you get boot failures, or just want to remove them, there are a few fixes. You can use a root explorer in android to go to /boot/ (make sure you have r/w permission) and delete the uImage.[ROM Name] file that you want to remove. Do not delete anything else in there. You can do the same in webOS with intrnalzpro, with master mode enabled.
I think moboot 0.3.5 is the current version. The rootzwiki thread for CM9 will have the most current version, I think.
Sent from my Galaxy S II (i777)
I though lvm can get porked when deleting partitions
And webdoctor acts up
so just in case i posted the rest maybe i misunderstood what he wanted lol sorry
and i though he was trying to delete cm to start fresh
no just the boot images in /boot
your anwser is the right one
and your right cm use the same partition no matter what
unless you made a partition for cm7 and one for cm9 i never done that
contents of .palm folder
Good morning guys... well I've been searching all morning for a thread to post my question and it seems there is some knowledge here....
anyway, here's my situation....
after booting into Android, my TouchPad scans the sdcard FOREVER, now I've cleaned out all and any kind of cache in all folders I know to clean, BUT in the .palm folder there are a few huge folders containing THOUSANDS of small files, so only thing I can think is that it's scanning those contents each boot.
I have looked all over the place and still don't have a clear understand of what those files are and how to go about logically getting read of what's needed and what isn't
Any help would be greatly appreciated
cdzo72 said:
Good morning guys... well I've been searching all morning for a thread to post my question and it seems there is some knowledge here....
anyway, here's my situation....
after booting into Android, my TouchPad scans the sdcard FOREVER, now I've cleaned out all and any kind of cache in all folders I know to clean, BUT in the .palm folder there are a few huge folders containing THOUSANDS of small files, so only thing I can think is that it's scanning those contents each boot.
I have looked all over the place and still don't have a clear understand of what those files are and how to go about logically getting read of what's needed and what isn't
Any help would be greatly appreciated
Click to expand...
Click to collapse
Take a look at this thread : http://forums.webosnation.com/hp-touchpad/307997-what-mega-huge-files-palm-folder.html
chicle_11 said:
Take a look at this thread : http://forums.webosnation.com/hp-touchpad/307997-what-mega-huge-files-palm-folder.html
Click to expand...
Click to collapse
Yeah I read that one and a couple more with the same info...
It sucks there's no way to identify what is and isn't needed in those folders... at least from what I have been able to find
Sent from my AOKP M6 TouchPad using TapaTalk 2
Here's an unusual situation. I've been searching for an answer for months now, to no avail.
My TP is the 32gb model. I have webOS 3.0.5 and the latest official cm9 nightly (right now it's the 8/19). I have (according to webOS system information and android settings>storage) 5.4 gb free. According to my math, it should be more like 16 gb. The only semi solution I've been able to find is to boot into webOS, open internalz pro, and look for the large files (that begin with ., making them hidden files) that are taking up space. That has not been successful. I imagine that if I run Acmeuninstaller to get rid of android, then do a clean install (using Acmeinstaller 2), that should solve the problem? I haven't bothered doing it since my tablet is working great, and why mess with something that is working so well?
BTW, the Ivm Ivscan commands mentioned a couple of posts up don't work in the executah terminal window. I get an Ivm not found error. I haven't bothered to hook up the tablet to my pc, that will probably be my next step.
If anybody has any suggestions, they'd be more than welcome.
Edit: The commands do work. I was using upper case I when I should have been using lower case l.... Duuuh!
chicle_11 said:
Here's an unusual situation. I've been searching for an answer for months now, to no avail.
My TP is the 32gb model. I have webOS 3.0.5 and the latest official cm9 nightly (right now it's the 8/19). I have (according to webOS system information and android settings>storage) 5.4 gb free. According to my math, it should be more like 16 gb. The only semi solution I've been able to find is to boot into webOS, open internalz pro, and look for the large files (that begin with ., making them hidden files) that are taking up space. That has not been successful. I imagine that if I run Acmeuninstaller to get rid of android, then do a clean install (using Acmeinstaller 2), that should solve the problem? I haven't bothered doing it since my tablet is working great, and why mess with something that is working so well?
BTW, the Ivm Ivscan commands mentioned a couple of posts up don't work in the executah terminal window. I get an Ivm not found error. I haven't bothered to hook up the tablet to my pc, that will probably be my next step.
If anybody has any suggestions, they'd be more than welcome.
Edit: The commands do work. I was using upper case I when I should have been using lower case l.... Duuuh!
Click to expand...
Click to collapse
Yeah I'm kinda feeling the same way... my TP is practically problem free... I hate to wipe webOS and Android clean... delete every file from SD storage and start over... but I'm like OCD about junk files in my storage because I use the robocopy command when I mount the TP in recovery to copy everything on there (and it has saved my tail several times)
Sent from my AOKP M6 TouchPad using TapaTalk 2
chicle_11 said:
Here's an unusual situation. I've been searching for an answer for months now, to no avail.
My TP is the 32gb model. I have webOS 3.0.5 and the latest official cm9 nightly (right now it's the 8/19). I have (according to webOS system information and android settings>storage) 5.4 gb free. According to my math, it should be more like 16 gb. The only semi solution I've been able to find is to boot into webOS, open internalz pro, and look for the large files (that begin with ., making them hidden files) that are taking up space. That has not been successful. I imagine that if I run Acmeuninstaller to get rid of android, then do a clean install (using Acmeinstaller 2), that should solve the problem? I haven't bothered doing it since my tablet is working great, and why mess with something that is working so well?
BTW, the Ivm Ivscan commands mentioned a couple of posts up don't work in the executah terminal window. I get an Ivm not found error. I haven't bothered to hook up the tablet to my pc, that will probably be my next step.
If anybody has any suggestions, they'd be more than welcome.
Edit: The commands do work. I was using upper case I when I should have been using lower case l.... Duuuh!
Click to expand...
Click to collapse
Well, I used Acmeunistaller, then did a fresh install using ACMEInstaller2 and the 8/19 nightly. It didn't solve my problem, I still have 5.4 gb free with 16 gb missing somewhere.
I think I'll have to doctor with 3.0.0 (it's the only doctor that handles partitions or something) then go to 3.0.5, the problem seems to be on the Webos side. I'll post the results after I do it (not today).
chicle_11 said:
Well, I used Acmeunistaller, then did a fresh install using ACMEInstaller2 and the 8/19 nightly. It didn't solve my problem, I still have 5.4 gb free with 16 gb missing somewhere.
I think I'll have to doctor with 3.0.0 (it's the only doctor that handles partitions or something) then go to 3.0.5, the problem seems to be on the Webos side. I'll post the results after I do it (not today).
Click to expand...
Click to collapse
Have you tried using Tailor which is a beta app in preware to format/manage various partitions.
This link will explain how to install Taylor, scroll down to Enabling the Beta Testing Feeds.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true .
This one explains how to use it there are 7 pages but I would suggest reading before you use Taylor. http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I hope this helps .
sstar said:
Have you tried using Tailor which is a beta app in preware to format/manage various partitions.
This link will explain how to install Taylor, scroll down to Enabling the Beta Testing Feeds.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true .
This one explains how to use it there are 7 pages but I would suggest reading before you use Taylor. http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I hope this helps .
Click to expand...
Click to collapse
I know about Tailor. That's why I prefer to use the doctor......
chicle_11 said:
Here's an unusual situation. I've been searching for an answer for months now, to no avail.
My TP is the 32gb model. I have webOS 3.0.5 and the latest official cm9 nightly (right now it's the 8/19). I have (according to webOS system information and android settings>storage) 5.4 gb free. According to my math, it should be more like 16 gb. The only semi solution I've been able to find is to boot into webOS, open internalz pro, and look for the large files (that begin with ., making them hidden files) that are taking up space. That has not been successful. I imagine that if I run Acmeuninstaller to get rid of android, then do a clean install (using Acmeinstaller 2), that should solve the problem? I haven't bothered doing it since my tablet is working great, and why mess with something that is working so well?
BTW, the Ivm Ivscan commands mentioned a couple of posts up don't work in the executah terminal window. I get an Ivm not found error. I haven't bothered to hook up the tablet to my pc, that will probably be my next step.
If anybody has any suggestions, they'd be more than welcome.
Edit: The commands do work. I was using upper case I when I should have been using lower case l.... Duuuh!
Click to expand...
Click to collapse
What a hassle!
Ran doctor 3.0.0, then 3.0.5. It took forever, and I still have the unexplained/missing 16 gb....
Related
[Q] Can't get my Touchpad to boot Android or WebOS, nor can I factory restore
Sorry if I should post this in the Dev thread. I've been through the forums, I've googled around, and none of the guides have helped solve this. I'll succinctly describe what I did and where I'm at. I had CM9 (oat's LnT ROM) and WebOS dual booting just fine. Since LnT was discontinued, I decided I'd see if maybe another ROM would work better since I was having issues. I put AOKP on via CWM. Now, however, both Cyanogen and AOKP showed up in my boot menu with Cyanogen as the default. One time I forgot to change what the boot was, and it tried (and failed) booting cyanogen. Since then, I can't boot anything. CWM can't mount anything, so I can't get to my nandroid backup, webOS won't boot. I'd honestly be happy with a pure factory reset and starting from scratch, but I can't get anywhere with webos doctor either. It fails at 8%: Oct 11, 2012 12:20:23 PM com.palm.nova.installer.recoverytool.CardController runnerFinished WARNING: flashing failed, move to failed card A found a guide at wwwDOTsouldevteamDOTnet/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad/ that looked promising, but I can't find any volumes: [email protected]:/# lvm.static vgscan --ignorelockingfailure Reading all physical volumes. This may take a while... [email protected]:/# Any advice or help would be most welcome.
stace said: Sorry if I should post this in the Dev thread. I've been through the forums, I've googled around, and none of the guides have helped solve this. I'll succinctly describe what I did and where I'm at. I had CM9 (oat's LnT ROM) and WebOS dual booting just fine. Since LnT was discontinued, I decided I'd see if maybe another ROM would work better since I was having issues. I put AOKP on via CWM. Now, however, both Cyanogen and AOKP showed up in my boot menu with Cyanogen as the default. One time I forgot to change what the boot was, and it tried (and failed) booting cyanogen. Since then, I can't boot anything. CWM can't mount anything, so I can't get to my nandroid backup, webOS won't boot. I'd honestly be happy with a pure factory reset and starting from scratch, but I can't get anywhere with webos doctor either. It fails at 8%: Oct 11, 2012 12:20:23 PM com.palm.nova.installer.recoverytool.CardController runnerFinished WARNING: flashing failed, move to failed card A found a guide at wwwDOTsouldevteamDOTnet/blog/2012/07/24/fix-bricked-hp-touchpad-recovering-software-bricked-touchpad/ that looked promising, but I can't find any volumes: [email protected]:/# lvm.static vgscan --ignorelockingfailure Reading all physical volumes. This may take a while... [email protected]:/# Any advice or help would be most welcome. Click to expand... Click to collapse This could be of help, though it's not complete, it's a start in the right direction. http://forum.xda-developers.com/showthread.php?t=1729179 Good luck. Edit : Here's another link that could help : http://forum.xda-developers.com/showthread.php?t=1426244
chicle_11 said: This could be of help, though it's not complete, it's a start in the right direction. http://forum.xda-developers.com/showthread.php?t=1729179 Good luck. Edit : Here's another link that could help : http://forum.xda-developers.com/showthread.php?t=1426244 Click to expand... Click to collapse Thanks for those links. Alas, the process in the second link presumes that the first command "vgscan" will find and identify a "store" volume. But mine doesn't find any volumes. I'll see if that author has any helpful advice on how I can create the volume group.
this should be a real simple fix. obviously you still have moboot working correct? and you are still able to boot into clockworkmodrecovery CWM correct? now im guessing by the "failed at 8% issue that youre likely on windows 7 64bit orr maybe even vista 64bit correct? do you have the android-sdk installed on your computer and are you familiar with how to enable ./adb connections? if yes then this should only take a few minutes to fix.
I have moboot, and can boot into CWM, but CWM complains about not being able to mount any dirs. I get the 8% issue whether I use Windows 7 64 bit or Mac OS 10.7. I'm sure I can muddle through adb connections. Do you have any tips for me to try? I can't successfully get the tablet to boot anything -- the closest is CWM which, as I say, can't mount anything.
Read only file system
My friends touchpad has the infamous read only file system. I have tried every forum post recommendation so far and nothing has worked. Webos loads but nothing can be changed and android will not boot. I got as far as removing the android partitions and resizing the webos partitions back to default using acmne uninstaller. After that it seems everything became complete read only. I luckly still have moboot and cw mod. I would like to just delete all partitions and volumes and start fresh. I tried the following commands : dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000 lvm.static pvcreate /dev/mmcblk0p14 lvm.static vgremove store but not matter what store is never actually removed even though it says its deleting it vgscan always sees it. I also tried wiping volume metadata no go. I tried fsck to repair file system tried the cm7 sd card fixer but since e: is gone because acmneuninstall happened to work before it went read only, it wont run. since its been so long I cant send it back to hp especially with hacks done to it. Were there any recent discoveries on repairing the read only issue, as long as its not hardware failure? thanks.
[Q] Strange memory problem (no "write" access)
Good evening guys, my TP started behaving very strange. It all started with a boot-looping android CM10 yesterday. Because I was in a hurry I then just booted webOS and did a short Google search. Today I tried to fix the problem, launched CWM and there started the problems: CWM tells me that /cache partition can't be opened/mounted. Strange. I tried a factory reset and a custom formatting of /cache using CWM. Nothing changed. CM10 is still loopin' around. Having a new idea I launched webOS and copied a new version of that CM10 ROM into the mounted internal storage (standard USB mode). Rebooted - started CWM - aand: there was no new file on /sdcard. I tried that around 5 times. Nothing changed. The strang thing: In "USB-mode" Windows-Explorer lets me copy files/delete files on it. They are even there if I refresh using "F5". After unmounting and mounting again - the files are gone.. Ok. I'm a smart guy and tried to remove a folder using Internalz Pro. Folder seems to be deleted. But after restarting my TP the folder reappeared. So I got that thought that my memory is somehow "damaged"? I searched the web and found webOS doctor. Tried it - it's stuck at 12%. It aborts with a nice stacktrace. ( http://pastebin.com/KycpiybA ). There was a "GNU bug" text somewhere, too. Did some more research and came to the conclusion that I have to repartion my TP. Ok. No problem. There are nice guides. The problem: I can't remove "store". Whenever I try to use that commands: Code: lvm.static vgscan --ignorelockingfailure lvm.static vgchange -ay --ignorelockingfailure lvm.static vgremove store I get no error messages - but "store" is still there. If I enter now: Code: lvm.static vgscan --ignorelockingfailure lvm.static vgchange -ay --ignorelockingfailure lvm.static vgcreate -s 8M store /dev/mmcblk0p14 I get: A volume group called 'store' already exists. Click to expand... Click to collapse Seems I really can't write to the memory? I guess it's dead now? Guys please help me! Thanks! EDIT: Oh almost forgot: I already tried ACMEUninstall - didn't change anything...
After some more research I found this thread: http://forum.xda-developers.com/showthread.php?t=1483066 Like I thought - it seems that the flash controller is damaged. Time to say Good Bye TP. I'm not sending it to HP cause I bought the device for only 120€ - repairing it would cost much more.
Touchpad stuck in a read only mode
I have a TP with WebOS 3.0.5, Moboot 0.3.8, and CM10.1. Whenever I reboot my device, any changes I make are reset. I can't load a new ROM. I can copy files to my SD Card and use them, but when I reboot, the files are gone. I see this is an ongoing issue. But most threads are old. Any fix for this? I just want to be able to run WebOS doctor now, but it won't work. It stops at 12% and says Unable to Reset. I have tried all the various WebOS doctor versions from 3.0.0 to 3.0.5. Thanks,
asif9t9 said: I have a TP with WebOS 3.0.5, Moboot 0.3.8, and CM10.1. Whenever I reboot my device, any changes I make are reset. I can't load a new ROM. I can copy files to my SD Card and use them, but when I reboot, the files are gone. I see this is an ongoing issue. But most threads are old. Any fix for this? I just want to be able to run WebOS doctor now, but it won't work. It stops at 12% and says Unable to Reset. I have tried all the various WebOS doctor versions from 3.0.0 to 3.0.5. Thanks, Click to expand... Click to collapse Use jcsullins hp TouchPad Toolbox. Complete reset.
Moody66 said: Use jcsullins hp TouchPad Toolbox. Complete reset. Click to expand... Click to collapse Cool thanks. This looks like it could be the thing. Do you recommend I do a Full Data Reset to delete both WebOS and Android, then Create WebOS Volume to prep the device for WebOS, then WebOS doctor to get back to factory? Then if all goes well, then re-install Android? I ask because the Full Data Reset sounds scary. I hope I can still access Moboot from there, for whatever that's worth.
Moody66 said: Use jcsullins hp TouchPad Toolbox. Complete reset. Click to expand... Click to collapse I posted in the Toobox thread, but just fyi, can you believe, Complete Reset didn't work! It's like my Touchpad is in read only mode.
asif9t9 said: I posted in the Toobox thread, but just fyi, can you believe, Complete Reset didn't work! It's like my Touchpad is in read only mode. Click to expand... Click to collapse Same exact thing is happening to me. Toolbox message says: Code: ERROR: LVM config erase check FAILED. Possible read-only failure. I have tried everything, and when it reboots, it is as if nothing changed. Check this out: Code: [email protected]:/# lvm.static vgchange -ay --ignorelockingfailure lvm.static vgchange -ay --ignorelockingfailure 11 logical volume(s) in volume group "store" now active [email protected]:/# [email protected]:/# lvm.static vgremove store lvm.static vgremove store Do you really want to remove volume group "store" containing 11 logical volumes? [y/n]: y y Do you really want to remove volu...... It says it's removed: Code: Logical volume "cm-data" successfully removed Volume group "store" successfully removed Then right after: Code: lvm.static vgscan --ignorelockingfailure Reading all physical volumes. This may take a while... Found volume group "store" using metadata type lvm2 STILL THERE!! LOL this is crazy... is it a hardware problem? NOTE: This touchpad was sitting dead for 6 months. Charged it, turned it on, read only ..
I'm sad but glad at the same time others are afflicted the same as me. It means others are trying to fix problem so we might get a solution. I have this beautiful touchpad sitting at home dead now. When it did work, it was in read only mode. But the battery died out again and now I can't get it started up at all. But I know the battery itself is fine because when it was working...in read only mode...the battery held charge really well.
asif9t9 said: I'm sad but glad at the same time others are afflicted the same as me. It means others are trying to fix problem so we might get a solution. I have this beautiful touchpad sitting at home dead now. When it did work, it was in read only mode. But the battery died out again and now I can't get it started up at all. But I know the battery itself is fine because when it was working...in read only mode...the battery held charge really well. Click to expand... Click to collapse I used a *touchstone to charge mine. I've heard that can make a difference. There are few threads on this read-only issue, but no fixes...
camaroqqq said: I used a touchpad to charge mine. I've heard that can make a difference. There are few threads on this read-only issue, but no fixes... Click to expand... Click to collapse Yeah the Touchstone worked the last time for me to charge it up. But it's not working anymore. Hard to believe two charging methods have failed at the same time. Either way I need to melt down the device to dispose of it because it has personal info and photos on it.
Getting same issues, been trying to sort for ages This is what the state of mine is Boots up Moboot 0.3.5 Cyanogenmod does not load just loops Does boot WebOS but Cannot Wipe the device, it reboots and nothing has changed, even removed a app and reboot and comes back again. tried toolbox complete wipe says read only mode WebOS Doctor recovery dies at 12% tried the Guide to recover and everytime I rescan, it finds the "store" yet again, even after I've deleted it. now confused, I can charge it too 100% with no issues, but found it best not to charge it on USB recovery mode, seems to charge ok from complete shutdown or in webos. but read only mode cant fix tried loads of stuff but seems every post with others with issues seems to go off on something else un-related from the issue.
Mine froze on Oct. 11 Yes, somewhat comforting to know that there are a few other cases of this. My first symptoms were that apps were starting to crash. Then I noticed that nothing I did would change the bootup state. Seems like a file system problem, but how could that information get overwritten at bootup? I hope one of the experts can shed some light on this problem. earthcoder said: Getting same issues, been trying to sort for ages This is what the state of mine is Boots up Moboot 0.3.5 Cyanogenmod does not load just loops Does boot WebOS but Cannot Wipe the device, it reboots and nothing has changed, even removed a app and reboot and comes back again. tried toolbox complete wipe says read only mode WebOS Doctor recovery dies at 12% tried the Guide to recover and everytime I rescan, it finds the "store" yet again, even after I've deleted it. now confused, I can charge it too 100% with no issues, but found it best not to charge it on USB recovery mode, seems to charge ok from complete shutdown or in webos. but read only mode cant fix tried loads of stuff but seems every post with others with issues seems to go off on something else un-related from the issue. Click to expand... Click to collapse
Well this sucks... I appear to be stuck with the same issue as everyone else in this thread. I mounted media volume in toolbox and used windows for format the drive. When I mounted it again the data was all still there...
I'm sad to say I trashed mine. Couldn't fix it. And didn't want to sell for parts because the memory had my personal data. Still haven't replaced the tablet because I can't find a better model for the price.
anyone ? Anyone was able to fix this ? somehow it can't mount to /data , I've tried all commands related lvm.static ( vgremove , lvremove..... ) it shows removed but after restart still there and nothing has changed. tptoolbox could not fix , could not remove partitions . acmeuninstaller and acmeuninstaller2 could not remove . is this hardware issue or software ?
What version of TPToolBox are you using? I haven't yet run across this problem in numerous wipes on (7) TPs. Had one that the Mobo had gone bad on - couldn't do anything on that one. Another had a video gremlin, but I was still able to wipe it. I wonder if maybe ADB and using shell commands might work? _Dan
TPToolbox issues
*UPDATE* It looks like I managed to recover from this completely. I ended up doing a second TPDebrick but I made sure I specified 32gb this time. I don't recall what I put in last time but I'm guessing it wasn't 32 and that is what wrecked my partitions. To preface, I had bricked my Touchpad and used TPdebrick to get it to boot again. I now have access to the boot menu and can get to TWRP and WebOS recovery just fine. However, TWRP won't let me install any .zips and shows 0mb on both the /system and the /data partitions. TPToolbox gives me a slew of problems such as : Install Android or Resize Android Volumes - Problem w/ vgchange -ay Repair Android Volumes - FAILED: rc=5: vgchange -ay Complete Data Reset - ERROR: Invalid partition info: end-gap greater than 1 percent of mmc I'm using the same TPToolbox v42 that I used to originally install Android on my Touchpad. Just to confirm the files hadn't corrupted somehow I redownloaded the toolbox and tried again to the same results. Any help would be appreciated. I'm pretty good with basic/intermediate Android stuff but I feel a little over my head with this stuff. *edit* I have since tried WebOS Doctor and it has told me it cannot fix my device either.
CriticalComposer said: *UPDATE* It looks like I managed to recover from this completely. I ended up doing a second TPDebrick but I made sure I specified 32gb this time. I don't recall what I put in last time but I'm guessing it wasn't 32 and that is what wrecked my partitions. To preface, I had bricked my Touchpad and used TPdebrick to get it to boot again. I now have access to the boot menu and can get to TWRP and WebOS recovery just fine. However, TWRP won't let me install any .zips and shows 0mb on both the /system and the /data partitions. TPToolbox gives me a slew of problems such as : Install Android or Resize Android Volumes - Problem w/ vgchange -ay Repair Android Volumes - FAILED: rc=5: vgchange -ay Complete Data Reset - ERROR: Invalid partition info: end-gap greater than 1 percent of mmc I'm using the same TPToolbox v42 that I used to originally install Android on my Touchpad. Just to confirm the files hadn't corrupted somehow I redownloaded the toolbox and tried again to the same results. Any help would be appreciated. I'm pretty good with basic/intermediate Android stuff but I feel a little over my head with this stuff. *edit* I have since tried WebOS Doctor and it has told me it cannot fix my device either. Click to expand... Click to collapse So glad you posted this. This is exactly what I did. When your mind is in all this other stuff thats going on its easy to forget that it could be as simple as this. Thanks!
I've got the exactly same problem. Had Evervolve Kitkat on my TP and I didn't charge it for a long period. After that I wasn't able to charge or wake it up again. With TPDebrick I could end in the boot menu, bu any further TPToolbox action failed. For me it seems, the necessary volumes are either not available or of size zero. I would like to revive the beloved TP, but have no glue how to overcome this situation @@@ SOLVED @@@ recreated volumes with this instructions WebOSdoctor 3.0.0 loading ... TPToolbox next