yashsingh1/xdaforums huggingface dataset:
[TouchPad General] HRTM:
Issues with resetting device using webos doctor 3.0.0

Hi,

This is my first post here. I'm having some issues with getting my touchpad back to factory conditions. These are all the things I did to mess up my TP:

1. Tried upgrading from Cyanogemod 9 to 10. Didn't get upgraded because of something I missed so I uninstalled the mod using ACMEUninstaller.

2. This one is the most stupid thing I could've done, when connecting my touchpad to my windows pc, it did not recognize it and asked me to format the drive and I went ahead and formatted it like a noob. Now, the touchpad wont boot. It goes to the hp logo and just stays there.

3. I followed each and every step from the first post in this thread and was able to remove and recreate the files and everything worked as it should.

4. After the mkdosfs -f 1 -s 64 /dev/store/media command, I put my TP on recovery mode and start the webos doctor version 3.0.0.

5. A couple of times the webos doctor gets stuck at battery charging and nothing happens. This happens when the USB connection with the PC is always maintained.

6. When run the webos doctor and connect the TP to my PC only after the doctor asks me to, it proceeds with resetting my device. This goes till 4%, then the TP goes back to the HP logo screen and the webos doctor says "Unable to reset device".

I'm on Windows 8.1 if that's something to be concerned about. Any help in resolving this issue is highly appreciated.

Thank you.
[TouchPad General] splashg:
Still no luck for me. Still, anything I do to the MMC on any level is ignored and the Touchpad returns to the state I started with.

It's like the thing is permanently stuck in read-only mode and I can't even write to it from the recovery image.

I get the same string everyone else does, so it's not the CSD register for the eMMC.
[TouchPad General] nlra:
Well, dang. So it is looking more and more like the problem isn't with the whole-chip write-protect that can be set in the CSD register. This means it is more likely related to the other write-protect mechanisms that exist in the EXT_CSD register.

Unfortunately, as far as I can tell, there is no way to read EXT_CSD via sysfs/debugfs on the version of Linux that is running on the Touchpad (2.6.35). I did find a set of userspace MMC tools (mmc-utils), but it sounds like they require Linux 3.0+ to work. So either we need to wait until somebody has managed to port a newer version of the kernel to the Touchpad, and then build a bootable-over-USB recovery image that contains the new kernel + the mmc-utils, or backport some of the changes in the MMC driver from Linux 3.x (it sounds like there is a specific ioctl that it needs to support for mmc-utils to work) to the current kernel and then roll a recovery image with that.

Ugh,

-- Nathan
[TouchPad General] tastyxda:
Just to echo the results being posted, here are my results:

My experience:

- Does boot WebOS,

- Cannot Secure Wipe the device, it reboots and nothing has changed.

- Attempted Android install but received errors.

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

- WebOS Doctor recovery dies at 12% no matter what

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

- I've also tried SCWells72 suggestion **

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

I then tried adding "-ff" and it errors as follows:

root@webos-device:/# lvm.static pvcreate /dev/mmcblk0p14 -ff
Really INITIALIZE physical volume "/dev/mmcblk0p14" of volume group "store" [y/n]? y
Can't open /dev/mmcblk0p14 exclusively. Mounted filesystem?

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

d00f00320f5903ffffffffff92404010

As it stands, not sure it would be a good idea to sell it on eBay. It has my private information on it, and I simply cannot remove any of it.
[TouchPad General] cooper104:
Amazing tutorial, I was ready to give up before seeing this post.. Thanks a million!
[TouchPad General] jdcrutch:
Novaterm says "command not found"

Thanks for this tutorial! I'm having trouble making it work, though, probably because I don't know a damned thing about Novaterm or Novacom. Since I hope never to have to use either program again, once I get my Touchpad working, I'm also hoping somebody will give me step-by-step instructions, so that I don't have to learn how to use them in all their wonderful intricacy. ;0)

I'm on a Win7 64x machine, so I'm using Novaterm in C:\Program Files\Palm, Inc\terminal. Novaterm starts up fine, but when I enter,

novacom boot mem:// < nova-installer-image-topaz.uImage

it responds

command not found

If I enter

run novacom boot mem:// < nova-installer-image-topaz.uImage

Novaterm responds,

variable novacom not found

I tried copying novacom.exe into the \terminal directory, but that made no difference.

That's as far as I can get. Any help will be much appreciated.
[TouchPad General] mh9:
I think you need to type 'novacom.exe' (without the single quotes), not just 'novacom', and use the first command above. So I believe it should be:

novacom.exe boot mem:// < nova-installer-image-topaz.uImage
[TouchPad General] Ai<3GG:
thanks to this, my touchpad was saved!
[TouchPad General] nathanotis:
I'm having the same issue, but I'm unable to connect via novacom. Any ideas what I may try?
[TouchPad General] jdcrutch:
Can't delete existing "store"

Thanks, mh9, but that wasn't the problem. In the Windows command window (formerly known as DOS), you don't have to enter the ".EXE" extension of an executable file. Same with the .BAT. extension of a batch file.

The problem was that the command "novacom boot mem:// < [and so on]" has to be entered into the DOS command window, not the novaterm window, as I'd been doing. But the novaterm window needs to be open and connected with the TouchPad.

Now I have a different problem.

I got to the root@webos-device:/# prompt, and started entering commands (for the 16GB TouchPad), but when I entered the "vgcreate" command, I got an error saying that "store" already existed. Apparently the "vgremove" command isn't actually removing anything, even though novacom tells me it is, and I've run it several times. (It does different things on the second and third executions, but when I try to move on, I get the same error.)

Any idea how to get around this?
[TouchPad General] mh9:
Sorry for the bum steer. I haven't used Windows for any of this in quite some time so should have kept my mouth shut.

Strange you are getting these errors because I just successfully executed everything in that first post on my 16GB TouchPad and it all worked without a hitch (Which is how I found your post in the first place.) I did all my work on Linux, but you are in a Novaterm window so that shouldn't matter. One thing I can think of. Are you copy/pasting those commands in Windows? Perhaps Windows is converting the -- (ascii double dashes) and/or the - (ascii single dashes) in the commands to single non-ascii characters? I've seen that happen before. And you are aware some of the commands have double dashes, some have single dashes and some have a mixture of both? (Not trying to insult your inteligence. The code in the quote window can be hard to make out.) Maybe try hand-typing each command from the beginning being very careful about the single/double dashes?

Hmm, what else?
[TouchPad General] jdcrutch:
Now I've Bricked My TP!

I read back through the thread and found that null0pointer was getting exactly the same errors that I had, so I tried what he or she was trying in #147. After "Really INITIALIZE physical volume "/dev/mmcblk0p14" of volume group "store" [y/n] y" didn't work, I decided to reboot and start over. She shut down just fine, but now nothing will wake her up again. My warranty's expired, but I've written HP to see what out-of-warranty service will cost me.

Any suggestions?

---------- Post added at 05:30 PM ---------- Previous post was at 04:45 PM ----------

No worries. As you'll see from my last post, it's more-or-less academic for me now, unless somebody knows how to wake up a bricked TP.
[TouchPad General] sstar:
Put it on a Touchstone charger if you have or can borrow one.
[TouchPad General] jdcrutch:
It worked!

It's like magic! Thank you!

But I gather I still have the fatal "read-only-TouchPad" problem, and I'm out of warranty. Anybody know whether or not HP will fix it, and, if so, what they'll charge me?
[TouchPad General] benru89:
damm it , i was hoping at the end of this thread someone would bring a solution for the read only hp touchpads...in my case i can boot to webos , but every change is made will be reverted upon reboot, tried to wipe partitions and it won't delete them...dont know what else i can try, i wish jcsullins or one of the major developers take a look a this, as there are a lot of people affected and it may not be so difficult since its not really bricked, i have access through novaterm and i can even boot webos.....
[TouchPad General] illest_one_7777:
I also get this. not sure if its the novaterm fie im using from the op but im stuck. this is frustrating but at east theres hope I get a the way here and thent his error appears

"Unhandled exception has occurred in your application. If you click Continue the application will ignore his error....... Arithmetic operation resulted in an overflow"
[TouchPad General] gunho1224:
How can i use on my TP 64gb?

Is it possible use on 64GB Touchpad?

Where need to change on script?
[TouchPad General] illest_one_7777:
can someone who got theres to work upload the novaterm.bat they used
[TouchPad General] mrputtputt:
same here. the novaterm.bat wasn't working. i was getting an jtw (or something like that error.

Question:

i ran unsintaller2. i then re-installed webos doctor (original). shouldn't that fix it the entire storage and bring back to original state? that's what i did a last year or year before i think. i've been running cm9 for quite a long time and upgraded to the evol version of jellybean.

doing this since there was a MTP issue and the jellybean/evol won't seem to connect via usb. so i might as well wipe it all.
[TouchPad General] geofwrig:
Read-only TouchPad and CSD register contents

Hi Nathan -- I am just seeing your thread now and am very interested in exploring this further. My 32GB TP appears to be in read-only mode as changes do not stick after a reboot. I have, as you guessed, installed Android (cm9,cm10.1). Your theory sounded promising but unfortunately as others have confirmed the CSD register looks to be in the correct state. I wonder what HP was actually doing with TPs that went back with this problem. I saw one post suggesting that HP staff had physically opened the device.

root@webos-device:/# cat /sys/class/mmc_host/mmc0/mmc0:0001/csd

d00f00320f5903ffffffffff92404010

Cheers.
[TouchPad General] ken2johnson:
Nice explanation of the research you did. Thank you for that. I have a Touchpad that is plagued by the Read Only mode. I went into the "adb shell" with Android booted and did the command you specified and got this as a result: d00f00320f5903ffffffffff92404010

Unfortunately, it looks the same as the one you got on your Touchpad. So, I think something else is the issue here. Android is actually the only thing that still boots properly on my Touchpad. WebOS is in a First Time Use state for some reason. Nothing I do seems to make a difference now.

Looks the same to me even though my Touchpad is in the Read Only mode.
[TouchPad General] nlra:
Guys,

I still don't have an explanation for you all yet, and I may never have an explanation for you (at least without the cooperation of Sandisk and HP; the CSD write-protect register field seemed like an obvious place to look but obviously didn't pan out). But one thing that makes tearing this problem apart hard is the fact that I have been fortunate in that my TouchPad has never displayed these symptoms, so I have never had direct contact with a failed device. I only started studying this problem because in the course of exploring how to install Android on the TouchPad, I ran into these stories, and I wanted to find out what was causing the issue (and even perhaps discover a way to fix it, if possible) so that I could actively avoid that fate for my own TouchPad while experimenting with Android myself.

It would definitely be easier to go exploring if I had access to a TP with a "dead" (read-only) eMMC. And even if I wanted to donate my own TouchPad to the cause, I cannot do to it whatever it is that makes these devices fail because we have no idea yet what even causes it to happen. So, if there is anybody out there who has given up hope and had already decided that they were going to throw their broken TouchPad in the trash, perhaps you might consider donating it to the cause of science by sending it to me instead? I'd be willing to cover postage.

Even with one in my hands, I cannot guarantee anything, but it does increase the odds.

-- Nathan
[TouchPad General] jockyw2001:
Hi guys, I have just finished my investigation of similar problems found on other cellphones and found out there is a register slice named SNDSK_HEALTH (this obviously stands for "Sandisk Health") in extCSD which can have values ranging from 1-5.

A value equal to 1 means the flash is in perfect condition. If it is 5, then the chip can no longer be erased or written.

The big question is if the chip can be reset or if the SNDSK_HEALTH value can be rewritten. I will do further experiments and let ya know.

/JockyW
[TouchPad General] MartinTheMartin:
Today I was looking if there is finally a way to fix my broken TouchPad that is lying around here for ages, and I stumbled upon your thread.

I run the test and I got the following value:

d00f00320f5903ffffffffff92404010

But my pad is indeed unfortunately in ReadOnly mode.
[TouchPad General] Gil1957:
Novaterm on Desktop

Hi

I put the novaterm on my desktop. Is that alright or do I have to activate it from the Palm, Inc folder?

Thanks
[TouchPad General] smiley rox:
where do i run those 16gb tp commands
[TouchPad General] mthous01:
Can't get WebOS Doctor 3.0.0 to work

I've completed all of the steps up to unning hte WebOS Doctor. When I run it, it flashes what looks like a command screen for an instant, and then nothing. Any ideas?

EDIT: So I figured it out, at least for me. I had only Java 7 installed on my computer. When I went back and installed Java 6 and directed the jar file to be run by javaw.exe in the Java folder, it ran without issue.
[TouchPad General] mexicano810:
Help please I am stuck

I got down to this step lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store

and I am getting this error:

Redundant stripes argument: default is 1

Please specify either size or extents (not both)

Run 'lvcreate --help' for more information

is this normal and should i continue or did I type something in wrong? Do I have to start Over?

is there spacing between M y? And that is a Capital i at the beginning right?

after every character i type in i get the overflow message that i have to keep hitting continue after every letter and space is there a way to turn that off it is taking me forever?

were is the spaces at maybe there is were i am messing up hard to tell were the spaces go

---------- Post added at 08:28 PM ---------- Previous post was at 07:54 PM ----------

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 "root@webOS device" this is good, now run these commands IN ORDER and these commands are CASE SENSITIVE

(For 32GB Touchpads only)

(16GB Touchpads)

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 :p)

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:

For those having problems with Java:[/QUOTE]

I got down to this step lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store

and I am getting this error:

Redundant stripes argument: default is 1

Please specify either size or extents (not both)

Run 'lvcreate --help' for more information

is this normal and should i continue or did I type something in wrong? Do I have to start Over?

is there spacing between M y? And that is a Capital i at the beginning right?

after every character i type in i get the overflow message that i have to keep hitting continue after every letter and space is there a way to turn that off it is taking me forever?

were is the spaces at maybe there is were i am messing up hard to tell were the spaces go:(:o:(
[TouchPad General] morningforest:
unable to run

can not run any help ??

same as many I have been runing cm 10.1 for some time I was going to update the root cert. LATE, i just found out about it I have not been booted into webos for some time . after updating cm to 10.2 . rebooted to webos

installed tailor when I was rebooting I KNOW I had the pw+home +v UP== dead TP. and have not

able to get it up and running . I had full batt. and have had it on the t stone charging for some time.

I have tryed tpdebrick many times . I can see the tp ubs . but can in get anyting on or off will not boot

at all DEAD.
[TouchPad General] jdcrutch:
Nathan can use my TP

I'd be willing to let you use my TP. Just get in touch.
[TouchPad General] ccheung:
I was having functional Touchpad. After several andriod rom updates, the wifi in andriod was not working but working in WebOS. Then I fully uninstalled all andriod and reset the WebOS. Now the Wifi was not working in WebOS too. I full downgraded the WebOS as instruction. It was sucessfully downgraded, but the wifi is still not working. I cannot pass the Wi-Fi setup page in WebOS. It simply cannot search any network.

Any idea or suggestion?
[TouchPad General] jas0nmc:
Read-only TP

Did Nathan ever get a read-only TP?
[TouchPad General] jdcrutch:
Not from me. I haven't heard from him. I'd still be willing to help.
[TouchPad General] Paul.ryan:
I have tried the method described in this thread but cannot get past the first command once in novaterm. I've searched this thread and done some google searching to no avail. Here is what my output in cmd looks like for the first few lines. I didn't think all was necessary as all of the commands return a similar error.

" c:\>cd program files\palm, inc

c:\Program Files\Palm, Inc>novacom boot mem:// < nova-installer-image-topaz.uIma

ge

c:\Program Files\Palm, Inc>novacom -t open tty://

root@webos-device:/# lvm.static vgscan --ignorelockingfailure

lvm.static vgscan --ignorelockingfailure

Reading all physical volumes. This may take a while...

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Volume group "store" inconsistent

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

WARNING: Inconsistent metadata found for VG store - updating to use version 17

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Automatic metadata correction failed

root@webos-device:/#

root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure

lvm.static vgchange -ay --ignorelockingfailure

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Volume group "store" inconsistent

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

WARNING: Inconsistent metadata found for VG store - updating to use version 17

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Automatic metadata correction failed

root@webos-device:/#

root@webos-device:/# lvm.static vgremove store

lvm.static vgremove store

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

WARNING: Inconsistent metadata found for VG store - updating to use version 17

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Automatic metadata correction failed

Volume group "store" not found

root@webos-device:/#

root@webos-device:/#

It seems as though there is no access to the sd card. The moboot bootmenu is still working as well as ClockworkMod and webOS recovery but neither webOS or Android will boot past the splash screen.

I have not tried the TPDeBrick option because I can still get into recovery and this problem seems to be a sd card access problem. I don't know where to go from here and am open to suggestions.
[TouchPad General] lk2121:
webosdoctor stuck at 8%

Hello, I need some help fix my TP which stuck while installing Android.

TP was stuck not doing anything while install android then I turned it off.

I tried webosdoctor but it was stuck at 8%.

We were unable to reset your device

Please go to HP support for help.

I tried HP support that wasn’t helpful.

I followed the all steps until I ran novaterm then showing this error messages.

root@webos-device:/# lvm.static vgscan –ignorelockingfailure

WARNING: Inconsistent metadata found for VG store – updating to use version 10

Incorrect metadata area header checksum

Automatic metadata correction failed

root@sebos-device:/# lvm.static vgchange –ay –ignorelockingfailure

Incorrect metadata area header checksum

Incorrect metadata area header checksum

Incorrect metadata area header checksum

Volume group “store inconsistence

Incorrect metadata area header checksum

Incorrect metadata area header checksum

WARNING: Inconsistent metadata found for VG store – updating to use version 10

Incorrect metadata area header checksum

Automatic metadata correction failed

I need any help to save my TP.

Thanks
[TouchPad General] sstar:
It might be worth trying jcsullins TP Toolbox in the developers forum you certainly have nothing to lose by trying.

All the best.
[TouchPad General] lk2121:
Thank you for advice.

I ran with TPToolbox and have this error message.

When I run Create webOS volume

>>>Obtaining existinf volume sizes .....

Determining volume sizes ....

Problem w/ vgchange -ay

Error: volsizes all failed rc=1

When I run Complete Data Reset

Incorrect metadata area header checksum on /dev/mmcblk0p14 at offset 31228690432

Incorrect metadata area header checksum on /dev/mmcblk0p14 at offset 31228690432

Incorrect metadata area header checksum on /dev/mmcblk0p14 at offset 31228690432

Incorrect metadata area header checksum on /dev/mmcblk0p14 at offset 31228690432

Incorrect metadata area header checksum on /dev/mmcblk0p14 at offset 31228690432

Warning: Inconsisent metadata found for VG store -updating to use version 10

Incorrect metadata area header checksum on /dev/mmcblk0p14 at offset 31228690432

Automatic metadata correction failed

recovery of volume group "store" failed

Failed: rc=5 lvm vgchange -an --ignorelockingfailure

What is wrong and how to fix it.

Thank you
[TouchPad General] biiip:
I have one that I still cannot unbrick.

here is the output

root@webos-device:/# cat /sys/class/mmc_host/mmc0/mmc0:0001/csd

d00f00320f5903ffffffffff92404010