Results 1 to 17 of 17
Like Tree2Likes
  • 1 Post By Willisme1
  • 1 Post By Carlos Moctezuma
  1.    #1  
    Hey,

    I have now resolved the issue, and I am posting my method for anyone to read... however, I should not be held responsible for any damage caused by running these commands yourself.

    You should probably read through this guide and see if you understand it first, since I didn't think of this myself, I simply used multiple guides to recover my TouchPad whilst I was desperate! There is probably a MUCH better way of doing this.

    Contents
    1. WebOS Internals Recover Page
    - 1.1. Debugging through Command Prompt/Terminal
    2. Constant Reboot after Doctor
    - 2.1. Entering Recovery
    - 2.2 Accessing the Linux Root
    - 2.3 Extracting the uImage
    - 2.4 Setting up for the uImage
    - 2.5 Using Novacom to push the uImage
    3. Recreating the Filesystem
    - 3.1 Read This!
    - 3.2 Filesystem commands
    - 3.3 The Next Problem
    - 3.4 Commands to mount/rw
    - 3.5 DOCTOR!

    1.
    The webOS Internals Recovery page is very useful, try that first.
    1.1. Trying running the Doctor from the Command Line, or Terminal to see what the issue is. To do so is simple, just make sure you have the latest Java installed, and then follow the webOS Internals guide:
    Quote Originally Posted by webOS Internals Recovery Page
    If you're running Windows, the java executable is probably not within the PATH environment variable. This means you need to first navigate to your java installation folder before running the webOS Doctor. On most systems it will be something like this:
    cd "c:\Program Files (x86)\Java\jre6\bin"
    java -jar <path to doctor-file>
    Now, whilst the doctor is running, you will see lots of lines streaming down the terminal/command prompt. You might spot a clear error, such as a Device not being found, or charging up to 25% before continuing.

    2
    Firstly, make sure you are having the same issue. I started with a fully charged TouchPad, stuck in a boot loop, restarting every 10 seconds. It appeared the Doctor was having trouble figuring out what had happened to my Partition Table.

    2.1 I booted it into recovery by holding the volume button whilst it was powering up. From here I had computer access to Bootie.

    2.2 Since we can't boot fully, we can't communicate with the root of the Touchpad, so to move from Bootie, directly into the Linux portion of the TP, we can push the uImage using novacom.

    2.3 Download your current webOS version Doctor, mine was 3.0.4. To extract the uImage, you must use a compression utility, I recommend jZip, but any tool such as winRar should work. Right click the .jar file, and open it through your chosen utility, and select the 'Resources' folder. At the bottom of the list in there, you will find 'webOS.tar', which you need to extract.
    Once that has extracted, find the uImage from within. It should be called 'nova-installer-image-topaz.uImage'. Extract this too.

    2.4 To push this image to the TouchPad, place the 'nova-installer-image-topaz.uImage' in the same directory as the Novacom command. In my case this was 'C:\Program Files\Palm, Inc'.

    Now that everything is set up, make sure you are in recovery mode, plug your TouchPad into the computer. Then boot Novaterm, by the following command:

    cd 'DIRECTORY OF NOVATERM'
    novaterm
    Novaterm was in the 'C:\Program Files\Palm, Inc\terminal' directory for me.

    2.5 You should then find a command prompt style window open, which is connected to your TouchPad through Bootie. However, it won't understand most commands. Run the command below, and it will begin to communicate with the true linux core, and can then accept these commands.

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

    3.
    3.1 Now that you can use normal commands, you can repair your filesystem. Since I don't know your specific problem, I can only provide you with the method of recreate the filesystem. You WILL lose all of your files doing this.

    3.2 To recreate the filesystem, simply execute the commands found here. This only shows how to recreate a 32GB filesystem, so do not attempt that if you have a 16GB TouchPad!

    For a 16GB file system, try the instructions at the end of the guide - credit goes to BlueSmokyWater, who posted with his own results on a 16GB TouchPad.

    3.3 Now that you have a filesystem, run the Doctor through the command prompt again, and you will see a new problem - the partitions cannot be mounted, and they are read only.

    3.4 Reboot the TouchPad into Recovery, and repeat steps 2.4 and 2.5. From here, I used the following commands to create mount points and make it read/write.

    mkfs.ext3 /dev/mapper/store-var
    mkfs.ext3 /dev/mapper/store-log
    mount -a
    mkdir /var/log
    mkdir /var/tmp
    mkdir /var/run
    mount -o remount, rw /
    3.5 Doctor the Touchpad, and cross your fingers!

    For a 16GB TouchPad:
    --------------------------------------
    a. lvm.static vgscan --ignorelockingfailure
    b. lvm.static vgchange -ay --ignorelockingfailure
    c. lvm.static vgremove store
    d. lvm.static vgscan --ignorelockingfailure
    e. lvm.static vgchange -ay --ignorelockingfailure
    f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
    g. lvm.static vgscan --ignorelockingfailure
    h. lvm.static vgchange -ay --ignorelockingfailure
    i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
    j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
    k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
    l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
    m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
    n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store

    NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
    o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store

    NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data partition,
    you can do more or less. 1 Physical Extent (PE) is 8MB.
    The number after -l is the number of Physical Extents for the partition.
    p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
    q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
    r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store

    NOTE: The following creates the media partition used as SDCARD and sets it to
    --minor 6, make sure you set it to --minor 6, the SDCARD is specified as dm-6
    in CM7. This will save you from having to edit /etc/vold.fstab in CM7.
    s. lvm.static vgscan --ignorelockingfailure
    t. lvm.static vgchange -ay --ignorelockingfailure
    u. lvm.static vgdisplay
    i. this command displays information on the Volume Group: store
    at the bottom you should see:
    Free PE/Size 851 / 6.65
    where X is the number of Physical Extents free and XX is the size free.
    ii. write down the number of X (Physical Extents free) to use in the next command
    v. lvm.static lvcreate -l 851 -M y --major 254 --minor 6 -n media store
    w. lvm.static vgscan --ignorelockingfailure
    x. lvm.static vgchange -ay --ignorelockingfailure
    y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
    z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
    za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
    zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
    Last edited by Willisme1; 01/10/2012 at 08:24 AM.
    old_geekster likes this.
  2. #2  
    Thank you so very much, my Touchpad is alive again!!!
  3.    #3  
    No problem! Did you get ArchLinux up and running btw? I just got it booting... It's amazing! I cannot wait for a full release
  4. #4  
    Quote Originally Posted by Willisme1 View Post
    No problem! Did you get ArchLinux up and running btw? I just got it booting... It's amazing! I cannot wait for a full release
    No I am still restoring all of my apps. I am going to fully setup WebOS again with patches, kernels, etc. Then I will install Archlinux and Android on the Touchpad.
  5. #5  
    Also, have you booted back into WebOS after installing Archlinux? And are there any issues?
  6. #6  
    Thank you so much! Its working again! Ive used this description:

    Quote Originally Posted by Willisme1 View Post
    Hey,


    1.
    The webOS Internals Recovery page is very useful, try that first.
    1.1. Trying running the Doctor from the Command Line, or Terminal to see what the issue is. To do so is simple, just make sure you have the latest Java installed, and then follow the webOS Internals guide:


    Now, whilst the doctor is running, you will see lots of lines streaming down the terminal/command prompt. You might spot a clear error, such as a Device not being found, or charging up to 25% before continuing.

    2
    Firstly, make sure you are having the same issue. I started with a fully charged TouchPad, stuck in a boot loop, restarting every 10 seconds. It appeared the Doctor was having trouble figuring out what had happened to my Partition Table.

    2.1 I booted it into recovery by holding the volume button whilst it was powering up. From here I had computer access to Bootie.

    2.2 Since we can't boot fully, we can't communicate with the root of the Touchpad, so to move from Bootie, directly into the Linux portion of the TP, we can push the uImage using novacom.

    2.3 Download your current webOS version Doctor, mine was 3.0.4. To extract the uImage, you must use a compression utility, I recommend jZip, but any tool such as winRar should work. Right click the .jar file, and open it through your chosen utility, and select the 'Resources' folder. At the bottom of the list in there, you will find 'webOS.tar', which you need to extract.
    Once that has extracted, find the uImage from within. It should be called 'nova-installer-image-topaz.uImage'. Extract this too.

    2.4 To push this image to the TouchPad, place the 'nova-installer-image-topaz.uImage' in the same directory as the Novacom command. In my case this was 'C:\Program Files\Palm, Inc'.

    Now that everything is set up, make sure you are in recovery mode, plug your TouchPad into the computer. Then boot Novaterm, by the following command:



    Novaterm was in the 'C:\Program Files\Palm, Inc\terminal' directory for me.

    2.5 You should then find a command prompt style window open, which is connected to your TouchPad through Bootie. However, it won't understand most commands. Run the command below, and it will begin to communicate with the true linux core, and can then accept these commands.

    3.
    3.1 Now that you can use normal commands, you can repair your filesystem. Since I don't know your specific problem, I can only provide you with the method of recreate the filesystem. You WILL lose all of your files doing this.

    3.2(### To recreate the filesystem, simply execute the commands found ###here. This only ###shows how to recreate a 32GB filesystem, so do not attempt that if you have a 16GB ###TouchPad!###)

    Instead of the code Ive used this code here: (probably to much code, but => worked for me!)

    --------------------------------------
    a. lvm.static vgscan --ignorelockingfailure
    b. lvm.static vgchange -ay --ignorelockingfailure
    c. lvm.static vgremove store
    d. lvm.static vgscan --ignorelockingfailure
    e. lvm.static vgchange -ay --ignorelockingfailure
    f. lvm.static vgcreate -s 8M store /dev/mmcblk0p14
    g. lvm.static vgscan --ignorelockingfailure
    h. lvm.static vgchange -ay --ignorelockingfailure
    i. lvm.static lvcreate -l 71 -M y --major 254 --minor 0 -n root store
    j. lvm.static lvcreate -l 8 -M y --major 254 --minor 1 -n var store
    k. lvm.static lvcreate -l 2 -M y --major 254 --minor 2 -n update store
    l. lvm.static lvcreate -l 3 -M y --major 254 --minor 3 -n log store
    m. lvm.static lvcreate -l 32 -M y --major 254 --minor 4 -n mojodb store
    n. lvm.static lvcreate -l 17 -M y --major 254 --minor 5 -n filecache store

    NOTE: THE FOLLOWING --minor JUMPS to 7 from 5 above
    o. lvm.static lvcreate -l 64 -M y --major 254 --minor 7 -n swap store

    NOTE: THE FOLLOWING MAKES CM7 PARTITIONS, I specified a 5GB cm-data partition,
    you can do more or less. 1 Physical Extent (PE) is 8MB.
    The number after -l is the number of Physical Extents for the partition.
    p. lvm.static lvcreate -l 96 -M y --major 254 --minor 8 -n cm-system store
    q. lvm.static lvcreate -l 32 -M y --major 254 --minor 9 -n cm-cache store
    r. lvm.static lvcreate -l 640 -M y --major 254 --minor 10 -n cm-data store

    NOTE: The following creates the media partition used as SDCARD and sets it to
    --minor 6, make sure you set it to --minor 6, the SDCARD is specified as dm-6
    in CM7. This will save you from having to edit /etc/vold.fstab in CM7.
    s. lvm.static vgscan --ignorelockingfailure
    t. lvm.static vgchange -ay --ignorelockingfailure
    u. lvm.static vgdisplay
    i. this command displays information on the Volume Group: store
    at the bottom you should see:
    Free PE/Size 851 / 6.65
    where X is the number of Physical Extents free and XX is the size free.
    ii. write down the number of X (Physical Extents free) to use in the next command
    v. lvm.static lvcreate -l 851 -M y --major 254 --minor 6 -n media store
    w. lvm.static vgscan --ignorelockingfailure
    x. lvm.static vgchange -ay --ignorelockingfailure
    y. mkdosfs -f 1 -s 64 -F 32 /dev/store/media
    z. mkfs.ext4 /dev/store/cm-system or mkfs.ext3 /dev/store/cm-system
    za. mkfs.ext4 /dev/store/cm-cache or mkfs.ext3 /dev/store/cm-cache
    zb. mkfs.ext4 /dev/store/cm-data or mkfs.ext3 /dev/store/cm-data
    ---------------------------------------------------------------

    3.3 Now that you have a filesystem, run the Doctor through the command prompt again, and you will see a new problem - the partitions cannot be mounted, and they are read only.

    3.4 Reboot the TouchPad into Recovery, and repeat steps 2.4 and 2.5. From here, I used the following commands to create mount points and make it read/write.



    3.5 Doctor the Touchpad, and cross your fingers!
    Last edited by Bluesmokywater; 03/27/2014 at 02:56 PM. Reason: (Edit)
  7. #7  
    Thank you! My friend was having the same issue and I'll send the link of your posting to her right now! ^^
  8.    #8  
    I've added the 16GB filesystem creation code from your post BlueSmokyWater, they could save someones TouchPad

    I'm glad a few people have found this helpful - I expected this problem become more common as more native linux builds come out
  9. jaydoc's Avatar
    Posts
    2 Posts
    Global Posts
    3 Global Posts
    #9  
    Hi

    First post on these forums.

    I had WebOS 3.0.5, CM7 alpha 3.5 and Arch linux installed on the TP. When trying to remove Arch and CM& and install CM9 my first step was to use webos doctor 3.0.5 to return TP to just webOS 3.0.5.

    WebOS doctor ran all the way to 82% and then said it was complete and done. But when I rebooted the TP all I got was boot loops at the HP logo stage. Multiple tries gave me the same result. When I run webOS doctor in a terminal, there don't seem to be any errors and everything looks like its completed, because at the end of the process, the terminal window has no error messages. I have tried this at least 5 times, after rebooting both PC and TP.

    When I came across this thread, I tried the suggestions below. However when I use novaterm to try to push the nova-installer-image-topaz.uImage file which I have placed in program files/palm,inc folder using the command "novacom boot mem:// < nova-installer-image-topaz.uImage" novaterm just does not recognize the command. It says unknown command. I am stuck at that step, again having tried it multiple times.

    Any suggestions..? Recharging the TP now.

    Thanks.
  10.    #10  
    Jaydoc, are you using that command from the command line, or novaterm?

    I believe you run that before you run novaterm... As in from the command line, or terminal on linux/mac.

    I say 'believe' because it has been a while since I have done this myself

    Hope I helped,

    Will
  11. jaydoc's Avatar
    Posts
    2 Posts
    Global Posts
    3 Global Posts
    #11  
    @Willisme1

    That was exactly what I had got wrong. I was typing the "novacom boot mem:// < nova-installer-image-topaz.uImage" from the novaterm window. When I used the command in the Windows terminal window everything went OK.

    I guess it would be a great help to others who make the same error to clarify that the command needs to be run in the Windows terminal. Maybe updating the first post could help.

    Anyway, thanks a ton.
  12. #12  
    Any knows if this is normal,

    In Step 2.5 y get this in novaterm console

    device_command_rx:502: got request: ve
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    parse_uimage:241: uimage 0x4100004c
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    parse_uimage:241: uimage 0x4100004c
    section_start 0x4100004c
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    parse_uimage:241: uimage 0x4100004c
    section_start 0x4100004c
    section_start 0x4132c888
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    parse_uimage:241: uimage 0x4100004c
    section_start 0x4100004c
    section_start 0x4132c888
    parse_uimage:241: uimage 0x4132c888
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    parse_uimage:241: uimage 0x4100004c
    section_start 0x4100004c
    section_start 0x4132c888
    parse_uimage:241: uimage 0x4132c888
    section_start 0x4132c888
    device_command_rx:502: got request: ve
    rb 'boot', url 'mem://', argc 0
    parse_uimage:241: uimage 0x41000000
    section len 3328060
    section len 11334126
    section len 0
    section_start 0x4100004c
    parse_uimage:241: uimage 0x4100004c
    section_start 0x4100004c
    section_start 0x4132c888
    parse_uimage:241: uimage 0x4132c888
    section_start 0x4132c888
    section_start 0x41dfba78

    And then cut the comunication is this correct or is something failing.

    Thanks in advance.
  13.    #13  
    Something is going wrong there I think, did you follow the first half of the guide to retrieve the correct uImage files?

    Also, do you have access to another computer?

    Whilst I compiled this guide - I'm not too tech savvy when it comes to the Command Line :s.

    I'll try to help though.
  14. #14  
    First Willisme, thank you for taking the time to put down clear and concise information.

    Two questions for whoever may have also used the recovery process in this thread.

    1. How long should the novacom boot mem://(imagefile) take to transfer? I have attempted it twice but the TP runs out of battery before the transfer is complete. This has always exceeded 7 hours. Usually seeing a transfer rate of 200 bytes/sec.

    2. I am able to connect to a working touchpad in Novaterm and I immediately get to root. However on the broken one it seems I am only able to get to the firmware. Does anyone know the command line to mount the usb or the nvram?



    Quote Originally Posted by Willisme1 View Post
    Something is going wrong there I think, did you follow the first half of the guide to retrieve the correct uImage files?

    Also, do you have access to another computer?

    Whilst I compiled this guide - I'm not too tech savvy when it comes to the Command Line :s.

    I'll try to help though.
  15.    #15  
    Did you get the uImage file from the location in the guide? When I did this, the image hardly took any time to transfer. I don't even recall thinking about the time.

    I know it's not too helpful me saying this, but since I really don't understand much about how the touchpad functions in the boot process, all I can say is have you tried a different computer? Or a different USB port?
  16. #16  
    I tried 3 different image files extracted from webos doctor 3.0.0 to 3.0.5. I even tried just using a 1k file to see how long that would take. The transfer is extremely slow which is just another confirmation of what I think is a hardware failure.

    Gonna try to see what else works. I do appreciate the quick response.
  17. #17  
    This is my first post but I come here from time to time. I am so glad I came across this procedure. After days of messing with my touch-pad I actually looked around to buy myself an android tablet. I actually follow the second part of the procedure and doctored in but was unsuccessful. Then I tried the first commands only after extracting the image from webos.tar and that did the trick. This should be the flagship procedure to bring back your touch-pad from the dead. Now all I need is the flagship to install cynogenmod into it, since there are a 100 procedures and none of them worked for me. That is how I ended up almost bricking my touch-pad. Thank you guys. You guys are awesome...
    HelloNNNewman likes this.

Posting Permissions