Android OS Forum banner
1 - 20 of 61 Posts

·
ResiDEV 3V0
Joined
·
53 Posts
Hey guys,

I feel the pain going through the internet with regards to our Touchpad and stalling with the latest SW.
Credit where credit is due, you can see a list in the DL suite.

I decided to make a file suite to make this easier.

Download the Suite here: http://dl.dropbox.com/u/58849669/Fix%20Your.....touchpad.zip
Download WebOS Doctor here: http://ws.hpwebos.com/webosdoctor

If your file system stops getting recognized by the Computer while in Android or WebOS, you are still messed up either way. You will have to do this eventually. It will destroy user Data, be sure you backed up recently...

1st Method (No SD card...period):

1. Back-up using Clockwork mod and export using Wifi or Bluetooth to your computer.
2. Moboot back into WebOS Settings -> Device Info -> Reset Options -> Full Wipe
(Optional Step: Boot into recovery mode, connect to computer, open command window in location of ACMEUninstaller and type " novacom boot mem:// < ACMEUninstaller " - its just safer to add this)
3. After the Wipe, Run WebOS Doctor.

2nd Method (8-12%):

1. Download the suite above
2. Install the Novacom Universal Drivers.
3. Move the Novaterm.exe and the TerminalControl.dll to C:\Program files (x86)\HP WebOS\SDK\bin after installing the novacom drivers.
4. Put the TP in Recovery mode (holding down power and vol+ at power-up)
5. Run WebOS Doctor and wait for it to stall at 12%
6. Open your command window and cd to the folder location of the ACMEInstaller
7. Run this in the command window: novacom boot mem:// < ACMEInstaller
8. When you see the ACMEInstaller stall and say that LVM failed, reboot by holding down power and home (the installer will force re-partition your device so webOS doc knows its not OK)
9. Boot back into recovery mode
10. Boot up WebOS Doctor and wait for the stall.
11. Open the command window again back to where the ACMEInstaller and other files are.
12. Run " novacom boot mem:// < nova-installer-image-topaz.uImage "
13. Once it reboots, put back into recovery mode.
14. For windows users: run command "novacom -t open tty://" *Now you are in the root!* Others just use "novaterm".
15. Run each of these commands individually: "lvm.static vgscan --ignorelockingfailure" ,"lvm.static vgchange -ay --ignorelockingfailure", and "mkdosfs -f 1 -s 64 /dev/store/media"

*IF YOUR DEVICE DYING AT 8%, You may want to use the fix_dos_fs.sh built in to completely repartition and reformat the disk before using the "mkdosfs" command. *

16. Reboot the device into recovery mode and Start up WebOS doctor and watch it work!

*If your device is still having trouble connecting over USB,but boots...RUN METHOD 1. That should fix it.*

ALSO POSTED ARE SEVERAL METHODS BY JSCULLINS (moboot guy - awesome) FOR IF YOUR SD CARD AND INTERNAL PARTITIONS ARE SEEN, BUT JUST ACTING UP.

http://rootzwiki.com...-sdcard-issues/

Say Thanks if this helped you!
 

·
ResiDEV 3V0
Joined
·
53 Posts
indeed JC, this is correct for when the SDcard is seen, but not recognized by the computer or Android correctly.

However, I found that it doesn't always work for when No SD card is seen (in Android or WebOS) or it just does not boot. This is basically what I found works if you installed Cyanogen and your system goes down. Just doing the techniques posted by WebOS Internalz does not work if you had Cyanogen.

Between your fine work (I am a fan) and these simple steps, it should be able to fix 99% of issues.

I wanted to put together a pile of everything one would need in one place with step by step instructions so that the less savvy could take care of the issue in less than an hour.
 

·
Android Beginner
Joined
·
7 Posts
Did it help you?

I have only been fixing the two touchpads that I own when delving a bit too hard into them. These have worked the most reliably for those issues.
Actually no it didn't... But If I would have found this write up 3 weeks ago it would have. I read your instructions and it matched what I did to fix my 12% error. I am sure this will come in handy to anyone else with issues. Seems like we have one or two every week with this problem.
 

·
Android Experiment
Joined
·
250 Posts
Excellent write-up and a tidy package. Between childofthehorn and jcsullins, you both have provided resources to repair most of the "near brick experiences" a lot of us have had. Big thanks to both of you.
 

·
Android Beginner
Joined
·
7 Posts
was240,

Tell me what your problem is and maybe I can help. Send me a PM.
Ohh I don't have a problem... I did have a problem a few weeks ago but with a google search I figured it out. The steps I took are exactly as you described. I did do one extra step... Once I did the webos doctor and booted to webos, I did a secure erase. Then I started from scratch.
 

·
Registered
Joined
·
1 Posts
I have a touchpad webos doctor stopped at 8%. The touchpad can boot into webos after a long booting time but no response for any touch. I tried 12% fix and it does not seem to work. I want to try fix_dos_fs.sh method in the thread. But I have no idea how to do it. Can someone provide some details about it. Where can I find fix_dos_fs.sh? What is the right command to run it?
 

·
Gadget Freak
Joined
·
194 Posts
Excellent thread childofthehorn. A couple of months back my TP got all screwed up and stopped at 12% with the doctor. I was fortunate enough to find a thread here by member Vmax and he had virtually the same instruction set as your method 2.

I had a feeling of great relief when after entering the commands in Nova and seeing the doctor go to 13% and beyond. Thanks.

Mike T
 

·
ResiDEV 3V0
Joined
·
53 Posts
Discussion Starter · #13 ·
Hey guys, I just moved the suite to being in my public dropbox folder. I might move to one of the Android File hosting services in the near future as a couple people said they got blocked out of public due to too many DL's.
 

·
ResiDEV 3V0
Joined
·
53 Posts
Discussion Starter · #15 ·
You need to check whether your novacom is installed. Try just typing "novacom" and hitting enter. If it tells you it isn't there, then re-install and reboot.

If you type novacom and hit enter and it come back with instructions for using novacom, you have it installed.

Please feel free to contact me via skype (under the same user name). I am available most of the time and can guide you from the very beginning to help you with your technical questions.
 

·
Registered
Joined
·
4,922 Posts
You need to check whether your novacom is installed. Try just typing "novacom" and hitting enter. If it tells you it isn't there, then re-install and reboot.

If you type novacom and hit enter and it come back with instructions for using novacom, you have it installed.

Please feel free to contact me via skype (under the same user name). I am available most of the time and can guide you from the very beginning to help you with your technical questions.
Fortunately, never have bricked a TouchPad. But, just to be on the safe side, I downloaded your suite and unzipped it. In this post you suggest to check whether one has novacom installed by typing "novacom" and hitting enter. I'm guessing that one has to be in the Palm, inc or WebOS/SDK/bin folder where the novacom.exe is located. I did this and I get "Unable to find device". I'm again guessing that if I had my TouchPad attached in "bootie" mode, that I would get the afore-mentioned instructions?

Line three in your instructions says: "3. Move the Novaterm.exe and the TerminalControl.dll to C:\Program files (x86)\HP WebOS\SDK\bin after installing the novacom drivers."

I think that you are assuming that everyone has the WebOS SDK installed on their computer as you did not include anything in your instructions about installing the SDK or how to do so. Is this a must have thing? Would putting these two files in the Palm, inc. folder work just as well which is where some folks have the novacom.exe. The UniversalNovacomInstaller and WebOSquickinstaller both create the Palm, inc folder and put the novacom.exe there.

I also see in the suite the nova-installer ulmage. Is this WebOS version specific or can you use this to repair any version of WebOS? I seem to remember reading somewhere that one had to extract that ulmage from the version of WebOS you were trying to fix or something like that.

Can you better explain the following:

*IF YOUR DEVICE DYING AT 8%, You may want to use the fix_dos_fs.sh built in to completely repartition and reformat the disk before using the "mkdosfs" command. *

So I think what you are saying is:

enter the following:

lvm.static vgscan --ignorelockingfailure
<press enter>
lvm.static vgchange -ay --ignorelockingfailure
<press enter>
But, before entering:
mkdosfs -f 1 -s 64 /dev/store/media

Enter this?
fix_dos_fs.sh

When that is done, then enter this?

mkdosfs -f 1 -s 64 /dev/store/media
<press enter>

Does any of this make any difference whether one is doing this on a 16GB or 32GB TouchPad?

And finally, please clarity this:

14. For windows users: run command "novacom -t open tty://" *Now you are in the root!* Others just use "novaterm".

Are you saying that I run this command instead of connecting to the Touchpad using novaterm? In instruction #3, you say to copy novaterm and the Terminalcontrol.dll in the WebOS/SDK/bin folder. Remember above I asked if putting then in the Palm, inc folder would be OK. I am guessing again that a Windows user would type in the cmd window: novacom -t open tty:// <press enter> and then run the commands I asked about above. Sorry if I got my questions out of order.

Hope I never have to use this information, but I want to be sure of the instructions and steps to take if I ever do.

Thanks
 

·
Registered
Joined
·
3 Posts
OMG! What the f*** is wrong with me?! I even bricked my kindle fire! This is like the worst thing ever. Never ever ever ever again am I going to mess with my damn electronics, well I don't have electronics anymore so can't mess with them even if I wanted to lol. BTW I do have novacom installed. I figured something out. When I try to run the command while webos doctor is running it won't work but once I close webos doctor and restart my touchpad into recovery mode and run the command it works. (I am assuming that it works because after running the command I see two penguins and text scrolling on the screen)
 

·
Registered
Joined
·
3 Posts
It worked! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! You have no idea how much this means to me. I really appreciate your help. Ok now let me go back and start messing with my touchpad and I also have to figure out a way to fix my kindle fire. Thanks again.
 

·
ResiDEV 3V0
Joined
·
53 Posts
Discussion Starter · #19 ·
I bolded my answers in-line.

Fortunately, never have bricked a TouchPad. But, just to be on the safe side, I downloaded your suite and unzipped it. In this post you suggest to check whether one has novacom installed by typing "novacom" and hitting enter. I'm guessing that one has to be in the Palm, inc or WebOS/SDK/bin folder where the novacom.exe is located. I did this and I get "Unable to find device". I'm again guessing that if I had my TouchPad attached in "bootie" mode, that I would get the afore-mentioned instructions?

Line three in your instructions says: "3. Move the Novaterm.exe and the TerminalControl.dll to C:\Program files (x86)\HP WebOS\SDK\bin after installing the novacom drivers."

I think that you are assuming that everyone has the WebOS SDK installed on their computer as you did not include anything in your instructions about installing the SDK or how to do so. Is this a must have thing? Would putting these two files in the Palm, inc. folder work just as well which is where some folks have the novacom.exe. The UniversalNovacomInstaller and WebOSquickinstaller both create the Palm, inc folder and put the novacom.exe there.

The SDK does give you some extra tools, many of the Novacom and Novaterm installers auto-install to that folder (even make the folder). That is because many are really just rips from the SDK. It also just ensures that you do not have problems as it might be looking for that file path.

I also see in the suite the nova-installer ulmage. Is this WebOS version specific or can you use this to repair any version of WebOS? I seem to remember reading somewhere that one had to extract that ulmage from the version of WebOS you were trying to fix or something like that.

This is an extracted uImage that is from the date of the first post. Generally, it does not matter what uImage version you use as long as its decently recent as the WebOS doctor will wipe over it anyway in doing the repairs. This basically just gives it a starting point for the Doctor to work from because it could find no reference as you wiped it. It is not as though you can simply throw on the uImage and it be all better as your partitions and other files are still messed up/corrupted.

Can you better explain the following:

*IF YOUR DEVICE DYING AT 8%, You may want to use the fix_dos_fs.sh built in to completely repartition and reformat the disk before using the "mkdosfs" command. *

Sometimes at 8% in newer builds, the terminal seems to be open at 8%, so you might not need this if you have updated your TP in the last 4-5 months. Just use the 12% method I outlined. I helped a few people over Skype doing this. Your partitions seem to be really messed up (beyond you just having windows repartition it) if you need to use the command sequence you listed above.

So I think what you are saying is:

enter the following:

lvm.static vgscan --ignorelockingfailure
<press enter>
lvm.static vgchange -ay --ignorelockingfailure
<press enter>
But, before entering:
mkdosfs -f 1 -s 64 /dev/store/media

Enter this?
fix_dos_fs.sh

When that is done, then enter this?

mkdosfs -f 1 -s 64 /dev/store/media
<press enter>

Does any of this make any difference whether one is doing this on a 16GB or 32GB TouchPad? NOT REALLY, once you Run the WEBOS Doctor its works on both (have 16gb and 2 32gb touchpads) the WebOS Doctor reads the IMEA and a few other points that are RO (tied to an onboard PROM) that show the real numbers. Kinda standard practice on 99% of mobile devices (even on computer mobo's).

And finally, please clarity this:

14. For windows users: run command "novacom -t open tty://" *Now you are in the root!* Others just use "novaterm".

Are you saying that I run this command instead of connecting to the Touchpad using novaterm? In instruction #3, you say to copy novaterm and the Terminalcontrol.dll in the WebOS/SDK/bin folder. Remember above I asked if putting then in the Palm, inc folder would be OK. I am guessing again that a Windows user would type in the cmd window: novacom -t open tty:// <press enter> and then run the commands I asked about above. Sorry if I got my questions out of order.

NOVATERM Does not connect to Root in the same way on Windows 7 machines (and some Vista, as well as XP pro). The command essentially force opens your Novaterm in Root for windows, which is why you still need novaterm and the .dll . Linux and Mac seem to open novaterm in root by default.

Hope I never have to use this information, but I want to be sure of the instructions and steps to take if I ever do.

Thanks
Did this help?
 

·
ResiDEV 3V0
Joined
·
53 Posts
Discussion Starter · #20 ·
It worked! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! Thank You! You have no idea how much this means to me. I really appreciate your help. Ok now let me go back and start messing with my touchpad and I also have to figure out a way to fix my kindle fire. Thanks again.
There are some Kindle Devs and remember that it is very hard to truly soft-brick your device.
Glad to help!
 
1 - 20 of 61 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top