THỦ THUẬT Đã có cách cứu HP touchpad bị kiệt pin anh em nhé

Thảo luận trong '[WebOS] Hỏi đáp - CSKN' bắt đầu bởi tena, 22/11/12. Trả lời: 7, Xem: 3281.

  1. tena

    tena Thành viên

    Hic, máy mình bị kiệt pin không ai giúp, làm thử các cách của anh em trên diễn đàn không thành công. Chiều nay mày mò trên internet tìm ra cách này của 1 bác nước ngoài, anh em chịu khó dịch nhé. Máy mình đã làm theo và đang chuẩn bị webOS được sau 1 tuần chết :D.

    Để vào chế độ QDloader mode: bấm power + home + volume down

    Driver kết nối máy tính để HP chạy chế độ QDloader đây: http://www.mediafire.com/?ypb1qi375aany98

    Mời anh em: http://rootzwiki.com/topic/36658-tpdebrick-v01/

    Cụ thể nội dung như sau:

    I have just uploaded TPDebrick v0.1: http://goo.im/devs/j...Debrick_v01.zip

    From the README:

    TPDebrick v0.1 by jcsullins
    ===========================
    TPDebrick is a set of files and scripts used to "de-brick"
    HP Touchpads. This process should allow the revival of Touchpads
    that cannot boot (only gives QDLoader mode) due to corrupted
    partitioning or bootloaders. Note that this should allow you
    to get into bootie (webOS) recovery mode. Additional steps
    may be needed after that to restore the bootie configuration or
    Operating System (i.e. webOS doctor).


    WHAT YOU WILL NEED:
    ===================
    1) Access to a Windows PC
    2) Access to a Linux PC
    3) Files from webOS Doctor (boot-genesis.tar.gz from webOS Doctor v3.0.5)
    4) QPST running/configured on the Windows PC
    5) A (bricked) Touchpad in Qualcomm Download (QDLoad) mode
    that has been left of the charger prior to beginning
    6) The files from this TPDebrick archive


    Obtain boot-genesis.tar.gz from webOS doctor:
    =============================================
    From http://www.webos-int...Doctor_Versions
    download the webOS Doctor v3.0.5 for Touchpad Wifi.
    (filename: webosdoctorp305hstnhwifi.jar)

    Create a new directory and unzip the webOSdoc jar contents into it.

    From the resources directory, untar the file webOS.tar (tar -xvf webOS.tar).

    Then extract the file nova-cust-image-topaz.rootfs.tar.gz
    (tar -xzvf nova-cust-image-topaz.rootfs.tar.gz ).

    Now, in the boot directory, grab the file boot-genesis.tar.gz
    and copy it some place safe.


    QPST and configuration
    ======================
    This process is based on a similar process created by
    darkspr1te on XDA forums in this thread:
    http://forum.xda-dev...92&postcount=89

    QPST, drivers and configuration info can be found in that thread.
    Note that the version of QPST known to work is: QPST 2.7 Build 374

    Configure QPST and connect the Touchpad.
    Start eMMC Software Download app.

    At top left, you should see "COMx Phone in Download Mode"
    (x will be the number of the COM port configured) to confirm
    that QPST is configured correctly (and your TP is ready).


    THE PROCESS
    ===========
    First we will flash a temporary bootloader to the Touchpad
    with QPST on Windows. This boatloader will make the Touchpad
    act as raw block device that we can read/write via USB. Then
    we will write the partitioning and bootloader data to the
    Touchpad with TPDebrick on Linux. You will need the TPDebrick
    archive on both the Windows and Linux PCs. You will also
    need the boot-genesis.tar.gz archive on the Linux PC.


    QPST on Windows
    ===============
    Extract the contents of the TPDebrick archive.

    Run the eMMC Software Download app if not already.

    At top left, you should see "COMx Phone in Download Mode".

    For "Flash Programmer file name" enter "EMMCBLD.HEX" (no quotes)
    For "Boot Image" enter "8660_msimage.mbn" (no quotes)

    Make sure "Program MMC device" is NOT selected

    Click "Search path 2" and "..." to the right of it to select
    the directory where the files from the TPDeBrick archive are
    located.

    Click "Download"

    Sample Output:
    --------------
    C:\Users\jc\Desktop\TPDebrick_v10\EMMCBLD.HEX
    C:\Users\jc\Desktop\TPDebrick_v10\8660_msimage.mbn
    Download completed - no errors detected
    Timeouts: 1st dev arrival 60000 ms, linger time 10000 ms
    DeviceArrival(DBT_DEVTYP_DEVICEINTERFACE) \\?\USBSTOR#Disk&Ven_Qualcomm&Prod_MMC_Storage&Rev_2.31#7&303f22f8&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
    DeviceArrival(DBT_DEVTYP_VOLUME) 00000010 0000

    The first two lines should be real quick and the rest should
    take around 30sec or so.

    Should now show "COMx No Phone Connected" at top left.

    If you see
    "You need to format the disk in drive E: before you can use it.
    Do you want to format it?" pop up,
    Select "Cancel"

    TPDebrick on Linux
    ==================

    First, make sure the Touchpad is not connected to the Linux PC.
    Then, run "ls /dev/sd?" and note the output.
    Connect the Touchpad to the Linux PC.
    Run "ls /dev/sd?" again.
    You should see a new entry. That is device we will use as the target
    of tpdebrick later (will be referred to as /dev/sdX).

    Extract the contents of the TPDebrick archive.
    Copy boot-genesis.tar.gz to the tpderick dir that was created.
    Go to the tpdebrick dir (cd tpdebrick).
    Run "tar -xzvf boot-genesis.tar.gz" to extract the files.

    If you have a 16GB Touchpad, run:
    sudo ./tpdebrick tp16 /dev/sdX

    If you have a 32GB Touchpad, run:
    sudo ./tpdebrick tp32 /dev/sdX

    NOTE: You may need to enter password to continue
    NOTE: Replace sdX as appropriate from above

    Sample Output (for 32GB)
    ------------------------
    [sudo] password for jc:
    Checking that config/files are valid... OK
    Checking that target is valid... OK
    Writing tz.mbn ... OK
    Writing bootie-topaz305.bin ... OK
    Writing emmc_appsboot.mbn ... OK
    Writing sbl3.mbn ... OK
    Writing rpm.mbn ... OK
    Writing ebr32.bin ... OK
    Writing sbl2.mbn ... OK
    Writing sbl1.mbn ... OK
    Writing mbr32.bin ... OK
    Done.

    REBOOT TOUCHPAD
    ===============
    Now, hold Power and Home buttons for 20 to 30 seconds to reboot.

    At this point you should be able to (at least) boot into recovery
    mode (bootie recovery with big USB symbol) by holding VolumeUp
    key to perform any additional recovery steps (i.e. webOS doctor).
     
    :
    thanhlongnet, letuan1982, huynt702 người khác thích nội dung này.
  2. minh_nguyen

    minh_nguyen Thành viên

    máy xài vẫn ok,nhưng thank bác vì nhiệt tình :D
     
    tena thích nội dung này.
  3. nova_ck

    nova_ck Denke anders

    Chúc mừng bạn đã cứu được "em nó". :)
     
    tena thích nội dung này.
  4. khongthevacothe

    khongthevacothe Thành viên

    mỗi lần mình bị kiệt pin thì khi gắn sạc vào nó hiện lên hình cục pin màu xanh đang sạc, lúc đó không khởi động được liền mà để khoảng 30'-1h mình khởi động thì ok, lần nào mình cũng làm vậy.
     
    huynt70 thích nội dung này.
  5. thanhlongnet

    thanhlongnet Thành viên

    máy mình bị con em nó chơi kiệt pin vài lần và giờ chỉ hiện đèn nút Home nhấp nháy để sạc cả đêm cũng ko ăn thua.em đang cố đọc bì của bác,thanks
     
  6. thanhlongnet

    thanhlongnet Thành viên

    theo như trang web nước ngoài hướng dẫn thì máy mình phải cắm vào PC chạy Linux đúng ko ak
     
  7. anhdepnhi

    anhdepnhi Thành viên

    có hướng dẫn cho win mà bạn, mình làm rồi xong hết các bước nhưng máy vẫn bị,chưa có tiến triển, bây giờ có bản 1.004 rồi, phải chạy ubuntu để cài TPdebrick.
    link đây bạn: http://rootzwiki.com/topic/38786-tpdebrick-v004/
     
  8. anhdepnhi

    anhdepnhi Thành viên

    mình khuyên bạn nên đi mua cáp khác chính hãng như nokia, samsung, htc ... đi bạn, lúc này còn cứu kịp đó, mua xong về cắm sạc là ok. Lúc mua nhớ đem máy thử coi có vô sạc ko nha bạn, mất công ko vô sạc tốn tiền :rolleyes:, ráng boot lên rồi vào web os nha, android kiệt pin là khó lên lắm, goodluck
    :)