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
Related
I am just about to give up any software solution and contact HP to see if they can fix this as a hardware problem.
But before I do that, i thought it might be worthwhile to post my problem here first.
My touchpad has been running fine, and operating without any problems until recently when I installed new apps or downloaded new files on the touchpad.
While the touchpad was up and running, everything was fine, the apps appeared in the menu, and the files copied could be accessed without any problems.
In terms of functionality there was nothing to suggest any problems with the TP.
However, whenever I reboot the TP (soft or hard reboot), all newly installed apps or files disappear and the TP reverts back to a previous state. Nothing that I do to the TP remains after a reboot.
So I downloaded the latest webosdoctor 3.0.5 to reset the TP but after getting to about the dreaded 12% mark, the webosdoctor fails, spewing out a lot of message about parted failure and something about the flash.
Following all the tips on using novacom to boot the uImage and accessing the TP from novaterm does not seem to work as any fix initiated is lost on the following reboot.
Even while logged in to the TP via novaterm, and using lvm.static to remove the logical and physical volume to see if I can get webosdoctor to recreate the partitions did not work.
The command lvm.static vgremove reported to successfully remove the logical drive, but on subsequent scan using lvm.static vgscan shows that the logical drive is still persistent.
Removing physical volume using lvm.static pvremove did not work.
In frustration I deleted /dev/mmcblk0p14 (and all the mmcblk0???). Consequently the lvm.static scans showed no logical drive available.... but on subsequent reboot they are all back.
Webosdoctor again failed with same problem when rebooted.
It seems like the TP is falling back to some default memory (partition) state and nothing that I do remains persistent. I can't see anyway I can force the partition tables to reset as any changes are lost on reboot.
So unless someone can suggest something different, I am resigned to having to call HP and send my TP in for repairs.
Does anyone else have similar experience?
P.S. this started after I updated to webOS 3.0.5 but I can't say this was the exact cause.
I have the same problem with my touchpad. Are there any solutions?
it looks like the only way to get it fixed is to contact HP and send your TP back for repairs.
I will be contacting them next week when I have time to organise for it to be repaired.
Have you tried to run the WebOS 3.0.0 Doctor? It will resize all of the partitions and leave you with a fresh copy of WebOS. It can be found here: "http://www.webos-internals.org/wiki/Webos_Doctor_Versions".
Here is what I did:
1.Completely shut down
2.Boot into recovery menu by holding Volume-Up button and then pressing the power button.
3.Run WebOS 3.0.0 doctor
If it halts for any reason, let me know what percentage it stopped on, and perhaps I can help you out.
As I have tried to outline in the OP, I have tried webosdoctoring from version 3.0.0 to 3.0.5
It doesn't have any effect as any changes to the partition is lost once the TP reboots.
I know webosdoctor 3.0.0 is the standard answer for all partition related problems, but I think in my case it is not a partition problem but more of the flash controller, that is hardware related. It might have gotten itself into a funny state where it is constantly going into fall back mode after every reboot.
I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.
colin_404 said:
I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.
Click to expand...
Click to collapse
This did not work for me. There is no way to remove /store
I'm having the same problem.
Device:
HP Touchpad 32 GB
WebOS: 3.0.4
Android: CM9 A2
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
What works:
- It loops while booting to Android
- It boots to Clockwork Recovery
- It boots to WebOS Recovery
- It boots to WebOS
- Everything works inside WebOS
- I can connect through Novaterm
What I've tried so far with no success:
- Recreating the file system
- Formating the internal storage
- Running a checkdisk
- Partitioning the storage
- Reinstalling Android
- Running WebOS Doctor 3.0.0, 3.0.4, 3.0.5
narci2500 said:
I'm having the same problem.
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
Click to expand...
Click to collapse
Nothing worked for me. Tried every trick suggested, even mixed things a bit. In the end I had to send it back to HP for it to be fixed.
All good now, it came back all fixed.
I'm having the same issue. Did they accept the return even with Android on it?
djteiwaz said:
I'm having the same issue. Did they accept the return even with Android on it?
Click to expand...
Click to collapse
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.
cychoi75 said:
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.
Click to expand...
Click to collapse
good to know, thanks
So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?
djteiwaz said:
So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?
Click to expand...
Click to collapse
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?
rr5678 said:
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?
Click to expand...
Click to collapse
Not yet. Should have it back by this weekend.
I also have this problem and have tried restoring my touchpad with numerous fixes on this site but they all fail and the touchpad just reboots to its previous state.
any help would be appreciated
Received it back. Would love some recommendations for possible fixes.
djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Okay. I'll gather some information now.
djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.
rr5678 said:
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.
Click to expand...
Click to collapse
Not a problem. I appreciate you spending time on this for me.
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.
Hello,
there was Android installed before. But because it didnt boot I uninstalled Android like in the guide(video).
When I now try to put something in cminstall folder or create new cminstall, there is this issue:
i can temporary(!) delete/create and everythings seems fine. But once i plug out Touchpad and plug in again, there are the same files like before.
When i try to install with ACME command i get at the end this error on the Pad:
Unable to create unique name
Unable to locate filesystem on device "/dev/store/media".
resizefat failed! Aborting! Please reboot
I have another issue with WebOS.
I can't use Preware. When starting Preware it loads some stuff first and then there is a message at the top left:
template load failed: main/main-scene.html
Thanks for your help!
Sounds like you need a webos doctor.
With WebOS Doctor it stops at 12% and says "We were unable to reset your phone. Please go to Palm Support for help."
When i reboot everything is like before.
GuelleX said:
With WebOS Doctor it stops at 12% and says "We were unable to reset your phone. Please go to Palm Support for help."
When i reboot everything is like before.
Click to expand...
Click to collapse
This should help
http://forum.xda-developers.com/showthread.php?t=1426244
It didn't help.
Same issue, it stops at 12%. But this time on pad, there is black chip on left AND hp logo in center after that. Before there was only one of it (don't remember which).
Also this command gives an "error": lvm.static vgcreate -s 8M store /dev/mmcblk0p14
The name is invalid or something (i can try it again and tell what it says exactly if necessary).
Any other suggestions?
Have you tried the touchpad toolbox tool that JC Sullins came out with recently? I used it the other day quickly and flawlessly. It can rebuild the volumes for Android and/or WebOS (yes, you can wipe WebOS from the touchpad). Give it a whirl.
Greetings, developers and friends!
My Touchpad is now stuck in a continuous boot, with Android backed up in Clockworkmod but I tried restoring and didn't work. A couple of days ago I deleted info on my SD card because it was too bogged down and didn't let me update anything. I did my best but I decided to do this,so I own it. Attempted to flash with Roland's video instructions and got all my files in order: Problem is, on the command prompt I get a message of "Device Not Recognized.
Here's what I see when booting:
Moboot 0. 3. 8
HP logo
boot ClockworkMod
boot Cyanogenmod
boot WebOS
boot webOS Recovery
reboot
shutdown
Then the screen goes light dark, as if the animation of CyanogenMod is going to be up and running but it doesn't. Is there a remedy to fix the SD card problem, maybe that will take care of it and my laptop can see the TouchPad? Backup works fine on ClockworkMod, restore does too but nothing happens.
Any takers? I have another HP tablet that I will not mess with, but I'd rather have both running Android.
Thanks,
chicawhyte
chicawhyte said:
Greetings, developers and friends!
My Touchpad is now stuck in a continuous boot, with Android backed up in Clockworkmod but I tried restoring and didn't work. A couple of days ago I deleted info on my SD card because it was too bogged down and didn't let me update anything. I did my best but I decided to do this,so I own it. Attempted to flash with Roland's video instructions and got all my files in order: Problem is, on the command prompt I get a message of "Device Not Recognized.
Here's what I see when booting:
Moboot 0. 3. 8
HP logo
boot ClockworkMod
boot Cyanogenmod
boot WebOS
boot webOS Recovery
reboot
shutdown
Then the screen goes light dark, as if the animation of CyanogenMod is going to be up and running but it doesn't. Is there a remedy to fix the SD card problem, maybe that will take care of it and my laptop can see the TouchPad? Backup works fine on ClockworkMod, restore does too but nothing happens.
Any takers? I have another HP tablet that I will not mess with, but I'd rather have both running Android.
Thanks,
chicawhyte
Click to expand...
Click to collapse
UPDATE: Was able to get through the Android removal, but it bothers me that one of the scrolling messages says, "no cminstall dir found, nothing to install.
chicawhyte said:
UPDATE: Was able to get through the Android removal, but it bothers me that one of the scrolling messages says, "no cminstall dir found, nothing to install.
Click to expand...
Click to collapse
TouchPad toolbox will solve it.
Moody66 said:
TouchPad toolbox will solve it.
Click to expand...
Click to collapse
Where is the Toolbox? Looked in Preware, Just Type and everywhere else and I can't find it. Thanks.
Found it on another thread, printed it out. Will take care of this after work. Thanks.
chicawhyte
chicawhyte said:
Found it on another thread, printed it out. Will take care of this after work. Thanks.
chicawhyte
Click to expand...
Click to collapse
It didn't work....aborted.... :crying:
It didn't, it aborted. I tried Roland's way and attempted to flash it but still the message is the same, no cminstall dir, power off when ready. Let me see if I can get a hold of him or JC (it'd be incredibly lucky for me) I hope my tablet can get the Android back.
Roland asked me about this, this is my reply. Feel free to help out.
chicawhyte said:
It didn't, it aborted. I tried Roland's way and attempted to flash it but still the message is the same, no cminstall dir, power off when ready. Let me see if I can get a hold of him or JC (it'd be incredibly lucky for me) I hope my tablet can get the Android back.
Click to expand...
Click to collapse
+Roland Deschain Ok Roland, what I have tried was to gain more memory on my tablet; there were several apps deleted, cached space, did all I could because I had an update via Goo.im. I tried to flash it but I was not successful; asides from that, there were automatic updates that the Touchpad did not allow due to low storage space.That is when I made the serious mistake of deleting the SD card.
I tried to uninstall according to your instructions and then load up the 5M to go back to full throttle, but for whatever reason when the scroll happened the messages were off-key, meaning that folders and files were not installed and not the usual way. That's when I realized there was trouble; I had made two Nandroid backups that are still in the Touchpad. I had only WebOS and no Android to be seen. I restored the most recent backup via ROM Manager and I thought that that would do the trick, still no Android (?).
I decided to try and reach out to my fellows at XDA-Developers because I try everything before I go to the forum; I know the rules there. That's when I was made aware of the Toolbox by JC Sullins and I downloaded it. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Thanks for your work and for helping us turn a good tablet into the best tablet around!
Greetings,
Please read below my message to Roland and my problem below/wanted to add that now on both computers (my laptop where I do the flashes) and my husband's where I copied the Palm, Inc. folder to attempt Android there-the message I get is that "there is no hardware found" on the command prompt.
Please try to follow the instructions and explain things when requested
chicawhyte said:
Hello Roland, help!!!!! Please read this thread and let me know if I have to wipe everything and restart from scratch with WebOS Doctor. Here's the thread from xda-developers: http://forum.xda-developers.com/hp-...r-boot-loops-deleted-sd-t2803190/post53886856. Runs WebOS fine, but no Android to be seen; files are there but it won't let me format the whole tablet. Thanks!
Click to expand...
Click to collapse
RolandDeschain79 said:
"Hey so I took a look but that just tells me you're confused and trying to follow multiple sets of instructions. Can you list what you've tried and where you get stuck. There's no cminstall folder in this set of instructions its a ttinstall folder. Did you complete the first steps of uninstalling android and wiping the USB drive?"
Click to expand...
Click to collapse
chicawhyte said:
+Roland Deschain Ok Roland, what I have tried was to gain more memory on my tablet; there were several apps deleted, cached space, did all I could because I had an update via Goo.im. I tried to flash it but I was not successful; asides from that, there were automatic updates that the Touchpad did not allow due to low storage space.That is when I made the serious mistake of deleting the SD card.
I tried to uninstall according to your instructions and then load up the 5M to go back to full throttle, but for whatever reason when the scroll happened the messages were off-key, meaning that folders and files were not installed and not the usual way. That's when I realized there was trouble; I had made two Nandroid backups that are still in the Touchpad. I had only WebOS and no Android to be seen. I restored the most recent backup via ROM Manager and I thought that that would do the trick, still no Android (?).
I decided to try and reach out to my fellows at XDA-Developers because I try everything before I go to the forum; I know the rules there. That's when I was made aware of the Toolbox by JC Sullins and I downloaded it. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Thanks for your work and for helping us turn a good tablet into the best tablet around!
Click to expand...
Click to collapse
Please try and limit your conversation to one location. People who spam my YouTube channel and the forum with the same questions tend to get permanently banned without warning. Consider this a warning.
chicawhyte said:
......That is when I made the serious mistake of deleting the SD card.
.......I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Click to expand...
Click to collapse
Secondly if I ask you a question try to answer it as completely as possible. Don't tell me you made a mistake by wiping the SDcard then refuse to tell me how you did this even after I asked specifically about it. Claiming that you know how to wipe the SDcard then asking for specific instructions how to do so doesn't give me confidence in your ability. If you wiped the SDcard from a windows PC then you've made your own problem and completely ignored all the available instructions.
chicawhyte said:
. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
Click to expand...
Click to collapse
I'm having a very hard time understanding why you say you're stuck on step 1, which is installing novacom and backing up your data, when you're talking about step 5 installing android???
Step by step instructions have been provided and I even made a long video that reads you all the info. No one can help you to follow instructions that's up to you. Saying you didn't want to follow the instructions then asking for help is just silly. If you do not wish to change the layout of your touchpad just stick to the Non data media roms.
New Super Easy Way Guide and video available
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"(DM & Non-DM)
*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