Page 1 of 5 12345 LastLast
Results 1 to 20 of 97
Like Tree19Likes
  1.    #1  
    Hi,

    A friend of mine gave me a dead Pre 3, in fact it doesn't boot anymore it only appears as QHUSB-DLOAD device when i plug it to a computer.

    I had read a lot of post about HTC with the same kind of problem, but hackers certainly prefer HTC rather than exPalm devices because they have solved the problem for them !

    I can't Doctor it, the screen is blank, no led, nothing except this QHUSB-DLOAD mode ...

    If someone have a clue ?

    Thanks.
  2. #2  
    Hi
    Had the same issue. No other option but send back for repair.

    Sent from my cm_tenderloin using Tapatalk 2
  3.    #3  
    Thanks for your answer but i need more optimistic one !

    The battery appears to be empty, i don't have the pinout but i can't find a voltage with my multimeter on it.
    But it can't be a clue a working Pre3 show something on screen without battery when USB is plugged, isn't it ?

    QPST is the software from Qualcomm (to talk to QHUSB-DLOAD device), but it didn't recognize the Pre3, it only show it as phone in download mode.
  4.    #4  
    Is omap3_usbload will works with pre3 ?
  5. #5  
    I will take a stab, if qhusb-dload is part of QPST diag, then one would need to use USB passthru to remove said diag mode.

    My Pre3 is not on my carrier but my PrePlus is, I download a prl from my carrier, then I put the PrePlus in diag mode via USB passthru, use qpst to backup my prl, then I disable diag mode on the PrePlus via USB passthru. Then on the Pre3 I invoke USB passthru put it in diag mode then use qpst to upload the new prl to my Pre3, then phone reboots, but USB diag mode is still enabled. One must go back into USB passthru to disable diag mode.

    As the modem has full control on the USB mode you can not reset the flash drive.

    If this is your issue, one must swap the USB board to another Pre3 rebuild the flash then swap back to get a working USB drive, then one can use USB passthru to disable diag mode.
  6.    #6  
    Quote Originally Posted by John Steffes View Post
    I will take a stab, if qhusb-dload is part of QPST diag, then one would need to use USB passthru to remove said diag mode.

    My Pre3 is not on my carrier but my PrePlus is, I download a prl from my carrier, then I put the PrePlus in diag mode via USB passthru, use qpst to backup my prl, then I disable diag mode on the PrePlus via USB passthru. Then on the Pre3 I invoke USB passthru put it in diag mode then use qpst to upload the new prl to my Pre3, then phone reboots, but USB diag mode is still enabled. One must go back into USB passthru to disable diag mode.

    As the modem has full control on the USB mode you can not reset the flash drive.

    If this is your issue, one must swap the USB board to another Pre3 rebuild the flash then swap back to get a working USB drive, then one can use USB passthru to disable diag mode.
    Thanks for your answer but no it is not my issue, mine is in download mode not in diagnostic mode !
  7.    #7  
    So, for now i need some help with QPST.

    What i have :

    Palm Pre3 (should have) a SNAPDRAGON S2 (MSM8255) CPU
    But in mantaray.xml (from webosdoctorp224mantawr.jar/resources/webOS.tar) a line says <CPU type="MSM7X30">
    So i admit that i can select this CPU for the bootloader choice (it's also a eMMC device)

    The JAR of webosdoctor contain some useful files needed to repair my Pre3
    (in webosdoctorp224mantawr.jar/resources/webOS.tar/mantarayumtsfw.tar/) :
    - partition.mbn
    - dbl.mbn
    - osbl.mbn
    - amss.mbn

    My Pre3 is stuck in QDL (Qualcomm Download Mode) but we still can talk to the phone, it is not dead even if whole flash is empty the PBL (Primary Boot Loader) is intact.

    QPST is able to flash those files to a phone in Download Mode but i've got some errors that i don't understand :
    1. from QPST 2.7-366 (last one) Software Download
    2. in Software Download i choose a BootLoader as Phone Image (i try few EMPRG7X30.HEX, MPRG7X30.HEX ...) if i press Start i have the error (with all HEX even the HEX from QPST) Could not determine the HEX scrambling method; the file is invalid.
    3. in Multi-image i select the folder with my *.mbn, choose Sec Boot 2.0 as Boot System
    4. But when i press Start QPST says Could not open Flash Programming File !

    Update 11th sept 2012

    Log files are friends, it gave what was behind the error : QPST's looking for a bootloader in the same folder as the mbn files and it must be EMMCBLD.HEX or eEMMCBLD.HEX (if Use Emerg. Host D/L is checked).
    So i rename MPRG7x30.hex to EMMCBLD.HEX and try again ... it doesn't works but go furtherer !
    2012/09/11 19:07:41.300 StartSB2Download
    2012/09/11 19:07:41.305 Begin SB2.0 Software Download
    2012/09/11 19:07:41.305 Skip Reset: 0
    2012/09/11 19:07:41.305 Lock phone
    2012/09/11 19:07:41.307 Examine phone mode
    2012/09/11 19:07:41.307 Get partition file name
    2012/09/11 19:07:41.307 Partition file (and path for flash programmer): C:\Users\thierry\Desktop\Partage\Pre3\partition.mb n
    2012/09/11 19:07:41.307 Flash Programmer file: C:\Users\thierry\Desktop\Partage\Pre3\EMMCBLD.HEX
    2012/09/11 19:07:41.308 Examine phone mode
    2012/09/11 19:07:41.308 Prepare to load the flash programmer
    2012/09/11 19:07:41.343 Initialize the downloader
    2012/09/11 19:07:41.343 Ping the downloader
    2012/09/11 19:07:41.343 Sending Ping Request
    2012/09/11 19:07:41.344 Response: 0x2 : Ticks: 0
    2012/09/11 19:07:41.344 Wait For Download Response Succeeded.
    2012/09/11 19:07:41.344 Get downloader parameters
    2012/09/11 19:07:41.345 Sending Flash Programmer Parameter Request
    2012/09/11 19:07:41.346 Wait For Parameter Response Succeeded.
    2012/09/11 19:07:41.346 Load the flash programmer
    2012/09/11 19:07:41.346 Search RAM image for erase pattern
    2012/09/11 19:07:41.346 Skipped search - base address equals start address
    2012/09/11 19:07:41.346 Using 32-bit write
    2012/09/11 19:07:41.346 Sent Write: Address: 0x80000000 Size: 0x100
    2012/09/11 19:07:41.353 Response: 0x2 : Ticks: 0
    2012/09/11 19:07:41.353 Wait For Download Response Succeeded.
    2012/09/11 19:07:41.353 Sent Write: Address: 0x80000100 Size: 0x100
    2012/09/11 19:07:41.359 Response: 0x2 : Ticks: 0
    2012/09/11 19:07:41.359 Wait For Download Response Succeeded.

    ...

    2012/09/11 19:07:45.512 Sent Write: Address: 0x80024600 Size: 0x8C
    2012/09/11 19:07:45.518 Response: 0x2 : Ticks: 0
    2012/09/11 19:07:45.518 Wait For Download Response Succeeded.
    2012/09/11 19:07:45.519 Sending Go Command 0x80000000
    2012/09/11 19:07:45.521 Response: 0x2 : Ticks: 0
    2012/09/11 19:07:45.521 Wait For Download Response Succeeded.
    2012/09/11 19:07:45.521 Finish switching to streaming download mode
    2012/09/11 19:07:45.521 SynchronizeConnection starting...
    2012/09/11 19:07:45.521 Sending Hello to flash programmer...
    2012/09/11 19:07:48.521 Timeout
    2012/09/11 19:07:48.521 Sending Hello to flash programmer...
    2012/09/11 19:07:51.521 Timeout
    2012/09/11 19:07:51.521 Sending Hello to flash programmer...
    2012/09/11 19:07:54.521 Timeout
    2012/09/11 19:07:54.521 Sending Hello to flash programmer...
    2012/09/11 19:07:57.521 Timeout
    2012/09/11 19:07:57.521 Sending Hello to flash programmer...
    2012/09/11 19:08:00.522 Timeout
    2012/09/11 19:08:00.522 Sending Hello to flash programmer...
    2012/09/11 19:08:03.522 Timeout
    2012/09/11 19:08:03.522 Sending Hello to flash programmer...
    2012/09/11 19:08:06.522 Timeout
    2012/09/11 19:08:06.522 Sending Hello to flash programmer...
    2012/09/11 19:08:07.511 Disabling automatic polling.
    2012/09/11 19:08:07.561 Try Hello with polling disabled...
    2012/09/11 19:08:07.567 Try Hello with polling disabled...
    2012/09/11 19:08:07.573 Try Hello with polling disabled...
    2012/09/11 19:08:07.579 SynchronizeConnection succeeded.
    2012/09/11 19:08:07.580 Sending Hello Packet
    2012/09/11 19:08:07.587 Version info = 3 2
    2012/09/11 19:08:07.587 Block size = 400
    2012/09/11 19:08:07.587 Flash base = 0
    2012/09/11 19:08:07.587 Device Name=eMMC:
    2012/09/11 19:08:07.587 Flash ID size= 4
    2012/09/11 19:08:07.587 Sectors = 128
    2012/09/11 19:08:07.587 Feature mask = 0x09
    2012/09/11 19:08:07.587 Sending Close 0
    2012/09/11 19:08:07.588 Cannot close when not previously opened
    #2012/09/11 19:08:07.589 ARMPRG error: 15, text: Cannot close when not previously opened
    2012/09/11 19:08:07.589 CloseDownloader error
    2012/09/11 19:08:07.591 Sending Security Mode 0
    2012/09/11 19:08:07.593 Decoding partition file
    2012/09/11 19:08:07.595 Sending partition file
    2012/09/11 19:08:07.595 Sending Partition Table
    2012/09/11 19:08:07.799 DBL image: C:\Users\thierry\Desktop\Partage\Pre3\dbl.mbn
    2012/09/11 19:08:07.800 Opening DBL file
    2012/09/11 19:08:07.801 Sending MI Open mode 15 size 0
    2012/09/11 19:08:07.803 No partition table received before open multi
    Ô2012/09/11 19:08:07.805 ARMPRG error: 15, text: No partition table received before open multi
    2012/09/11 19:08:09.060 Download end, status 103, error 783
    2012/09/11 19:08:09.060 Exit SB 2.0 download with status 0x00000000
    In fact the log is right we must send a partition table, partition.mbn contains the MBR only, but how ?

    For this guy it looks simple : http://www.anyclub.org/2012/05/how-t...nto-blank.html but it doesn't works for me !
    Last edited by dadwarf; 09/12/2012 at 01:48 PM.
  8. #8  
    Not near my computer but you need the latest version of QPST, the older version can not handle the CDMA/SIM combo, if that is not the issue, then I am not sure.
  9.    #9  
    Quote Originally Posted by John Steffes View Post
    Not near my computer but you need the latest version of QPST, the older version can not handle the CDMA/SIM combo, if that is not the issue, then I am not sure.
    Thanks for your answer, i have the last version (2.7-366) ...
  10. #10  
    Just bumping this I have now two touchpads also stuck with only qdownload mode.
  11. #11  
    Quote Originally Posted by paddyponchero View Post
    Just bumping this I have now two touchpads also stuck with only qdownload mode.
    Bricked bootie webOS device owners, keep the faith!!!!!!!

    The information in this thread has given me some faint hope for reviving 2 bricked TP GO's I have on hand.

    I do understand the steps the author of this blog post details. He didn't document things very well but its enough to move forward after some revisions are made. I am in the process of rewriting the steps so they may work with WebOS devices.
    anyclub.org ----- Dancing Android: How to program eMMC images into blank flash with USB only in MSM7630

    That process will also include steps from dadwarf's post above in this thread.
    Dead Pre 3 (QHUSB-DLOAD mode) - "Need help with QPST"

    The spark that helped me put this all together (in my head at least) can be found inside the readme file for the latest QPST. It now supports the APQ8060 and APQ8460 and there are many things in that readme file which when viewed in conjunction with the two posts I referenced above make the idea of getting palm bootloader restored via USB (without having the JTAG pinout available for use with one of those flashers in a box solutions) sound very plausable, more so that any other method I've heard about or tried.

    Hold on for a little while for some sort of process document coming me. I'll need to test it out after i put the steps all together. If someone else see's the things I see after reading through the documents I refer to and wants to embark on creating a process flow for web OS devices, feel free. My spare time is limited for stuff like this and it might take me a week or more to get it written and tested.
    Last edited by TopTongueBarry; 09/13/2012 at 01:50 PM.
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
    dadwarf, Rnp, Sanjay and 2 others like this.
  12.    #12  
    Quote Originally Posted by TopTongueBarry View Post
    Bricked bootie webOS device owners, keep the faith!!!!!!!

    The information in this thread has given me some faint hope for reviving 2 bricked TP GO's I have on hand.

    I do understand the steps the author of this blog post details. He didn't document things very well but its enough to move forward after some revisions are made. I am in the process of rewriting the steps so they may work with WebOS devices.
    anyclub.org ----- Dancing Android: How to program eMMC images into blank flash with USB only in MSM7630

    That process will alos include steps from dadwarf's post above in this thread.
    Dead Pre 3 (QHUSB-DLOAD mode) - "Need help with QPST"
    Finally, the spark that helped me put this all together (in my head at least) can be found inside the readme file for the latest QPST. It does now support the APQ8060 and APQ8460 and there are many things in that readme file which when viewed in conjunction with the two posts I referenced above make the idea of getting palm bootloader restored via USB (without having the JTAG pinout available for use with one of those flashers in a box solutions) sound very plausable, more so that any other method I've heard about or tried.

    Hold on for a little while for some sort of process document coming me. I'll need to test it out after i put the steps all together. If someone else see's the things I see after reading through the documents I refer to and wants to embark on creating a process flow for web OS devices, feel free. My spare time is limited for stuff like this and it might take me a week or more to get it written and tested.
    Great ! I feel not alone :-)

    Your right the readme of QPST can be useful !
    I tried few version of PRG7x30.HEX found on the web with the same result.
    I checked manually partition.mbn and it matches with the partition table described in mantaray.xml.

    How QPST know where flashing *.mbn files ?
    Is there a way to upload and execute from memory the webOS bootloader ?
  13.    #13  
    If we found the source code of the bootloader (MPRG7x30.hex) we could be able to send command without QPST but i can't find the source code !
  14. #14  
    Quote Originally Posted by dadwarf View Post
    Great ! I feel not alone :-)

    Is there a way to upload and execute from memory the webOS bootloader ?
    Yes, detailed here in the OMAP boot Procedure:
    Last Resort Emergency BootLoader Recovery - WebOS Internals
    I haven't had any luck getting omap3_usbload (TI OMAP3 USB boot ROM tool, version 0.1) to detect the snapdragon processor used in Touchpad and Touchpad GO devices. If you have not already tried this method to boot your Pre 3 via USB, I recommend you do. It may work.

    I do remember reading of someone who had successfully connected to their Pre or Pre 2 using omap3_usbload, the downloaded the bootloader, but couldn't figure out how to run and load it over USB. I have searched the forums here recently and can't seem to loacte the threads any more.

    TTB
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  15.    #15  
    Quote Originally Posted by TopTongueBarry View Post
    Yes, detailed here in the OMAP boot Procedure:
    Last Resort Emergency BootLoader Recovery - WebOS Internals
    I haven't had any luck getting omap3_usbload (TI OMAP3 USB boot ROM tool, version 0.1) to detect the snapdragon processor used in Touchpad and Touchpad GO devices. If you have not already tried this method to boot your Pre 3 via USB, I recommend you do. It may work.

    I do remember reading of someone who had successfully connected to their Pre or Pre 2 using omap3_usbload, the downloaded the bootloader, but couldn't figure out how to run and load it over USB. I have searched the forums here recently and can't seem to loacte the threads any more.

    TTB
    Nice try but it isn't a Texas Instrument CPU in Pre3 and TouchPad but a Qualcomm ;-)
  16. #16  
    Reviving this thread -

    Anyone have any success getting the palm bootloader restored via USB on a Pre 3 or Touchpad (Qualcomm CPU) that only has QHUSB-DLOAD mode available?

    I have two TP GO's who's lives depend on this ......
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
  17. #17  
    Quote Originally Posted by TopTongueBarry View Post
    Reviving this thread -

    Anyone have any success getting the palm bootloader restored via USB on a Pre 3 or Touchpad (Qualcomm CPU) that only has QHUSB-DLOAD mode available?

    I have two TP GO's who's lives depend on this ......
    Not that I know of...

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  18. #18  
    Bringing a Pre 3 , Touchpad, or Touchpad GO (Qualcomm CPU) device back from the dead isn't going to be easy. I've gotten stuck dozens of times so far.

    There is now a glimmer of hope as XDA's darkspr1te has managed to get into a dead powerless MSM8660 that only had QHUSB-DLOAD mode available and download a bootloader to it. He used QPST as we suspected would be necessary. Here's the link to the XDA thread. Despite the mention of JTAG in the thread's title, he did not have the pinout, he used QPST without a JTAG connection:

    http://forum.xda-developers.com/show...0#post33017800

    I am having another brain fry experience from all of this. If anyone here has the ability to take the process XDA's darkspr1te is working on, modify or tweak it so we can use it to restore the bootie (bootloader) on our HP/Palm devices please step forward. (Rod - webOS Internals folks, Tom - webOS Ports folks - can you hear me calling .......... ????)

    There are differences. The device he's working on has 29 partitions. Our's don't have that many (13 or 14 are the numbers that come to my mind presently, like I said, this problem and the research / attempts to resolve it have me brain fried)

    One thing we don't need to worry about is a backup of the device and partition data he claims is necessary for the device he is working on. We'll only need to get the webOS bootie loaded and running so we'll have novacomd/novaterm access. We could then set up the filesystems from novaterm and use webOS doctor or a previously made memboot backup to return our presently dead webOS devices to functionality.

    I'd really appreciate help with this ....

    Thanks,
    Barry
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
    MartinH@webos likes this.
  19. #19  
    Can we directly dump the first few megabytes of the flash? I always wanted to yank a copy of my tokens. I'm assuming bootie is a 2nd or 3rd stage bootloader, since it has access to some of the hardware devices, etc.

    Update: You know what, the XML in the Chinese article linked look oddly similar to trenchcoat.xml. Maybe someone should reverse engineer Trenchcoat and see if it provides any hints on where things are stored?
  20. #20  
    Quote Originally Posted by GMMan View Post
    the XML in the Chinese article linked look oddly similar to trenchcoat.xml. Maybe someone should reverse engineer Trenchcoat and see if it provides any hints on where things are stored?
    This discovery is definately worth investigating!

    Others who take a peek at darkspr1te's work in the thread posted above and note anything that might help, please feel free to chime in here. Any thoughts or ideas that might lead to us getting the webOS bootie loaded on HP/Palm devices stuck with only access to QHUSB-DLOAD mode are appreciated.

    Thanks,
    TTB
    ----------------------------------------------------------------------------------------------------
    I am an AT&T employee and the postings on this site are my own and donít necessarily represent AT&Tís positions, strategies or opinions.
Page 1 of 5 12345 LastLast

Posting Permissions