[Help] Touchpad will NOT boot into recovery. What now?

[UWPVIOLATOR]

I see. I know what caused the brick it was the repeated process of restoring 3.0.4 as it would never complete 100%. Now that I found out how to resume after it fails I could fix it but now I just need to get back into recovery.

 

[Mutoidi]

If you were getting up to 80% restore on 'Dr' then perhaps there is an 'easy' solution, yes.

Back to full charge, USB plugging and button pushing???

 

[UWPVIOLATOR]

Back to full charge, USB plugging and button pushing???

Is this a question? What gets me is if I plug the USB into my computer and press Power+Home+Vol up I hear the ding that a driver was detected by my computer. If I continue to hold it I hear a double ding as an error. So its not dead. It is doing something. I wounder if I do the boot into "OMAP boot Procedure" if that is when it can be detected.

I have Windows 7 Ultimate. Is it telling me to boot into linux or can I do this with in windows?

OMAP boot Procedure

First, ensure that the Linux SDK and novacom packages are installed, as you will need to run webOS Doctor as the final step in this process. Second, ensure that you have a copy of the webOS doctor jar ready for your phone.

Download: omap3_usb.tar.bz2. If you have not libusb 0.1.3 installed on your computer, install it. It is needed for the header file /usr/include/usb.h On Ubuntu, make sure you have the libusb-dev package installed.

If you have a Pre 2, you need to change the ProductID in the code to 0xd00e

Compile on Linux system with "make". Optionally install with "sudo cp omap3_usbload /usr/local/bin"

Now extract the bootie binary from a WebOS Doctor image: (note: webosdoctor file name will vary)

mkdir doctor; cd doctor; unzip ../webosdoctor.jar; cd resources
mkdir webOS; cd webOS; tar xvf ../webOS.tar; mkdir nova-cust-image-castle.rootfs; cd nova-cust-image-castle.rootfs
tar xvzf ../nova-cust-image-castle.rootfs.tar.gz ./boot/boot.bin; cd boot

Booting bootie over USB:

Ensure USB is unplugged from the Pre, and remove the Pre's battery.

On your Linux system, run:

sudo omap3_usbload boot.bin

This should return:

TI OMAP3 USB boot ROM tool, version 0.1
......

and a series of dots while it looks for an OMAP3 to send boot code to.

Now, plug the pre into USB.

If all works as it should, the usbload program should return:

found device!
download ok

And your Pre will now show a USB logo. (this is bootie's "Recovery mode")

Put the battery back in without unplugging the USB.

Since you are now in USB recovery mode, you should be able to run the webOS doctor on the host Linux box. Remember that the SDK novacom package must be installed for the webOS Doctor to work in Linux.

One way to do this is to launch the doctor from the command line like:

sudo java -jar webosdoctor.jar

And follow the usual steps to recover your pre's operating system from here.

 

[Mutoidi]

It was a suggestion with question marks after it.. thus giving you the choice of decision.

If you have the Novacom drivers successfully installed you may be able to open Linux Command line under 'Tools' in WOSQI.. otherwise the Win. Command prompt should allow you to access the TP Directory? (That's another suggestion, with a question mark after it).

The above (your post #23) may only be applicable to the 'Pre' Phone as already mentioned.

If you have need of yet further specific infos relative only to the TouchPad, why not post your query directly @ webOSNation?

I wish you luck with it!

 

[UWPVIOLATOR]

Thank you. I did post over there and no response yet. I keep reading that you cant brick the TP but then the only things I read about recovering is button combinations which don't seem to be working on my end. If all else fails I am going to call up HP and tell them that while my TP was updating it turned off and would not come back on.

 

[Mutoidi]

No worries.. sorry I can lead you to a more direct and immediate solution.
I am sure the 'non-bricking' refers largely to 'non-Androided' machines anyway..

OK.. good luck with HP if you choose that 'route'.

 

[UWPVIOLATOR]

So update. In device manager TP shows up as QHSUSB_DLOAD or Palm. Finding people talking about it but no fixes yet

 

[Mutoidi]

As 'greenskinredeyez' points out to you @ webOS Nation (below).. perhaps the Novacom Drivers now need reinstalling? (Suggestion with question mark after it).

Also you may like to respond by answering the question posed to you there: '..Do you have CM7 installed?..' as it may bear some relevance to the type assitance that is being offered.

http://forums.webosnation.com/hp-to...pad-will-not-boot-into-recovery-what-now.html

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

'..To prevent fake brick, you've got to keep the touchpad charged. Plug the 5.3v charger (not the normal usb charger) into your touchpad. Hit home+Power for long enough to reset it. Let it charged to full power. Then, a couple of things to look at:

(a) Is the webosdoctor file corrupted? It happned to me once before. Try to login to your profile and download webosdoctor 3.04 there. Try this first before you go to (b). Also try to reinstall novacom using the right version (64 bit (X64, for win 7) or 32 bit (X86 - for XP) using the method I mention below in your quote "jar -> zip").

(b) If after using a fresh copy of webos doctor file you are still not successful, disable internet security when you try it the next time.

(c) Make sure the USB cable is good.

(d) Reinstall java?

Keep the touchpad fully charged.

Do you have CM7 installed?

Good luck.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~