Page 5 of 5 FirstFirst 12345
Results 81 to 97 of 97
Like Tree19Likes
  1. kocoman2's Avatar
    Posts
    1 Posts
    Global Posts
    6 Global Posts
    #81  
    where to find these files?

    EMPRG7X30.HEX, MPRG7X30.HEX

    thanks
  2. #82  
    Quote Originally Posted by nichtwirklich View Post
    Oh okay, du find out which device it is (for other reading the thread):

    after you connected your phone in mass storage mode, type

    dmesg

    output should be sth like this
    Code:
    [127459.080991] sd 12:0:0:0: [sdg] Attached SCSI removable disk
    [127538.911224] sd 12:0:0:0: [sdg] 11452416 512-byte logical blocks: (5.86 GB/5.46 GiB)
    [127538.912857] sd 12:0:0:0: [sdg] No Caching mode page present
    [127538.912862] sd 12:0:0:0: [sdg] Assuming drive cache: write through
    [127538.916059] sd 12:0:0:0: [sdg] No Caching mode page present
    [127538.916064] sd 12:0:0:0: [sdg] Assuming drive cache: write through
    here /dev/sdg is your device.

    To your problem, okay you dont have a working Pre3? Do you?

    After the partition table is written, you have to baykup by dd partition 1, 2, 3, 5, 6, 9, 11, 12 from a working Pre3 and restore it by dd to the broken.

    Problem is the copyright, if you dont have a second Pre3 and the token/modem partition 7 and 8. You cannot "create" them and you cannot use the same with two Pres3.

    What did you do, that your phone ended up in Download mode? In my case it was a accident at writing the boot logo. I could proof it later, one tga file wasn't readable on the flash /media/internal) and trenchcoat aborted and killed everything. I was so stupid to reboot after the third try failed.

    Maybe your flash is broken?

    Teamviewer is doable, I live in Europe, so your evening is to late for me, weekend sounds okay.

    I sent you a message bro, lets skype then teamview bro ... I want to fix this issue ... thanks
  3. #83  
    Quote Originally Posted by terroar1776 View Post
    I sent you a message bro, lets skype then teamview bro ... I want to fix this issue ... thanks
    My Pre 3 just died and won't get to Recovery Mode/USB logo either... So count me in as another who's hoping you guys can perfect this process and come up with a concise walkthrough (hopefully without requiring a second Pre 3)...
  4. #84  
    I've collected some tools and such (including extracting the .mbn files from webosdoctorp224mantaatt.jar and procuring EMMCBLD.HEX - which should be just a renamed MPRG7X30.HEX). No readme yet (well, I haven't had any success in recovering my bricked Pre3), but at least the files are safe and in one place.

    You may get them via anonymous FTP from my server:

    ftp://ftp.2rosenthals.com/pub/webOS/Pre3/

    I've also included QPST 2.7.366, the Qualcomm USB driver version 2.0.3.9, and revskills.

    HTH
    MAMISHO likes this.
  5. #85  
    Quote Originally Posted by LewisR View Post
    I've collected some tools and such (including extracting the .mbn files from webosdoctorp224mantaatt.jar and procuring EMMCBLD.HEX - which should be just a renamed MPRG7X30.HEX). No readme yet (well, I haven't had any success in recovering my bricked Pre3), but at least the files are safe and in one place.

    You may get them via anonymous FTP from my server:

    ftp://ftp.2rosenthals.com/pub/webOS/Pre3/

    I've also included QPST 2.7.366, the Qualcomm USB driver version 2.0.3.9, and revskills.

    HTH
    THANK YOU FAM!!!! I hope I can try this, this weekend AGAIN!!!! I miss my pre 3
  6. #86  
    I have a Pre3 with the same problem and a working Pre3 to backup the partitions needed.

    Looks like I'm to dumb to follow the instructions mentioned here (Maybe because I *never* used Linux...).
    Could someone help me to fix my Pre3?
  7. #87  
    Quote Originally Posted by oskar leopold View Post
    I have a Pre3 with the same problem and a working Pre3 to backup the partitions needed.
    Me too - in Germany. I now have the same QHSUSB_DLOAD situation with my Pre3 AT&T 16 GB (with modified European config).
    This Pre3 became very wet after happy rains - and the battery and so was still in the device for several hours.
    Now the Pre3 is disassembled and getting dryer - but the is no sign of live - but this QHSUSB_DLOAD behaviour.
    I have no idea if and which parts of the device are broken because of the rain.

    I have more working Pre3 devices available - but I have never debrick a Pre3.
    Perhaps I should first find out what parts are still working and what is broken?
    Any advices are welcome !
  8. #88  
    Quote Originally Posted by LewisR View Post
    I've collected some tools and such (including extracting the .mbn files from webosdoctorp224mantaatt.jar and procuring EMMCBLD.HEX - which should be just a renamed MPRG7X30.HEX). No readme yet (well, I haven't had any success in recovering my bricked Pre3), but at least the files are safe and in one place.

    You may get them via anonymous FTP from my server:

    ftp://ftp.2rosenthals.com/pub/webOS/Pre3/

    I've also included QPST 2.7.366, the Qualcomm USB driver version 2.0.3.9, and revskills.

    HTH
    Thanks for the files. I'm for sure in the same boat with a "for parts" Pre3 I bought. Gonna see if I can make this happen...
    Follow me on Twitter
    For the latest webOS news check out pivotCE
    Remy X likes this.
  9. #89  
    Quote Originally Posted by terroar1776 View Post
    Hey Nichtwirklich, I just followed your procedures im stuck now after using qpst, flashing the mbn files and hex but qpst and my computer no longer read my PRE 3 as a phone ... when I connect it throught USB, QUALCOMM CDMA TECHNOLOGIES MSM pops up and im stuck on mass storage ... how do I get out of this part?

    Thank you so much my pre 3 DIED AGAIN, if i get this working ill brick it again to make a youtube tutorial to help the others :P ... so please help me get out of this fam

    Terroar1776
    I am at the exact same place. It tries to communicate with the device after the flash but can't. So without touching ANYTHING I reboot into my Ubuntu install.

    Quote Originally Posted by nichtwirklich View Post
    Here it is, I modified the LVM layout a little bit

    Don't use this bootsector, if you must backup your media partition.

    You need to know which /dev/sd is your Palm (try dmesg after you connected the Pre3 with your PC). Usually it is /dev/sdb

    so this line:

    Code:
    dd if=hp-pre3-bootsector-1k-with-dd.bin of=/dev/sdb bs=1k count=1
    after this just reboot, the phone should reach a stage where you can use the webos doctor.
    I can't do any of this because I cannot determine which /dev/sd my Pre3 is using. I checked dmesg and get a lot of this:
    [ 98.364364] usb 3-1: new full-speed USB device number 2 using ohci-pci
    [ 113.501578] usb 3-1: device descriptor read/64, error -110
    [ 128.742867] usb 3-1: device descriptor read/64, error -110
    [ 128.982753] usb 3-1: new full-speed USB device number 3 using ohci-pci
    [ 144.119777] usb 3-1: device descriptor read/64, error -110
    [ 159.361137] usb 3-1: device descriptor read/64, error -110
    [ 159.601068] usb 3-1: new full-speed USB device number 4 using ohci-pci
    [ 170.009774] usb 3-1: device not accepting address 4, error -110
    [ 170.145878] usb 3-1: new full-speed USB device number 5 using ohci-pci
    [ 180.554677] usb 3-1: device not accepting address 5, error -110
    [ 180.554857] hub 3-0:1.0: unable to enumerate USB device on port 1
    [ 181.144276] init: anacron main process (952) killed by TERM signal
    [ 181.974777] usb 3-1: new full-speed USB device number 6 using ohci-pci
    [ 197.112114] usb 3-1: device descriptor read/64, error -110
    [ 212.353235] usb 3-1: device descriptor read/64, error -110
    [ 212.593266] usb 3-1: new full-speed USB device number 7 using ohci-pci
    [ 227.730436] usb 3-1: device descriptor read/64, error -110
    [ 242.971554] usb 3-1: device descriptor read/64, error -110
    [ 243.211634] usb 3-1: new full-speed USB device number 8 using ohci-pci
    [ 253.620328] usb 3-1: device not accepting address 8, error -110
    [ 253.756448] usb 3-1: new full-speed USB device number 9 using ohci-pci
    [ 264.165192] usb 3-1: device not accepting address 9, error -110
    [ 264.165406] hub 3-0:1.0: unable to enumerate USB device on port 1
    [ 264.377268] usb 3-1: new full-speed USB device number 10 using ohci-pci
    [ 279.514511] usb 3-1: device descriptor read/64, error -110
    [ 294.755591] usb 3-1: device descriptor read/64, error -110
    [ 294.995640] usb 3-1: new full-speed USB device number 11 using ohci-pci
    [ 310.132747] usb 3-1: device descriptor read/64, error -110
    [ 323.633935] usb 1-1: new high-speed USB device number 6 using ehci-pci
    [ 338.747103] usb 1-1: device descriptor read/64, error -110
    [ 353.964283] usb 1-1: device descriptor read/64, error -110
    [ 354.180296] usb 1-1: new high-speed USB device number 7 using ehci-pci
    [ 369.293468] usb 1-1: device descriptor read/64, error -110
    [ 382.778513] usb 1-1: new high-speed USB device number 8 using ehci-pci
    [ 397.891691] usb 1-1: device descriptor read/64, error -110
    [ 413.108892] usb 1-1: device descriptor read/64, error -110
    [ 413.324810] usb 1-1: new high-speed USB device number 9 using ehci-pci
    [ 428.438047] usb 1-1: device descriptor read/64, error -110
    [ 443.655237] usb 1-1: device descriptor read/64, error -110
    [ 443.871254] usb 1-1: new high-speed USB device number 10 using ehci-pci
    [ 454.279969] usb 1-1: device not accepting address 10, error -110
    [ 454.392066] usb 1-1: new high-speed USB device number 11 using ehci-pci
    [ 464.800737] usb 1-1: device not accepting address 11, error -110
    [ 464.800917] hub 1-0:1.0: unable to enumerate USB device on port 1
    [ 465.076880] usb 3-1: new full-speed USB device number 12 using ohci-pci
    [ 480.213989] usb 3-1: device descriptor read/64, error -110
    [ 495.455167] usb 3-1: device descriptor read/64, error -110
    [ 495.695193] usb 3-1: new full-speed USB device number 13 using ohci-pci
    [ 510.832324] usb 3-1: device descriptor read/64, error -110
    [ 526.073571] usb 3-1: device descriptor read/64, error -110
    [ 526.313635] usb 3-1: new full-speed USB device number 14 using ohci-pci
    [ 536.722245] usb 3-1: device not accepting address 14, error -110
    [ 536.858341] usb 3-1: new full-speed USB device number 15 using ohci-pci
    [ 547.267065] usb 3-1: device not accepting address 15, error -110
    [ 547.267186] hub 3-0:1.0: unable to enumerate USB device on port 1
    [ 548.703295] usb 3-1: new full-speed USB device number 16 using ohci-pci
    [ 564.316585] usb 5-1: new high-speed USB device number 2 using xhci_hcd

    This is what df shows:
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/sda9 19438876 10835096 7593300 59% /
    none 4 0 4 0% /sys/fs/cgroup
    udev 1695628 4 1695624 1% /dev
    tmpfs 341276 1164 340112 1% /run
    none 5120 0 5120 0% /run/lock
    none 1706368 9148 1697220 1% /run/shm
    none 102400 36 102364 1% /run/user
    /dev/sda7 90099 35320 47970 43% /boot

    I'm not sure what to try at this point.
    Follow me on Twitter
    For the latest webOS news check out pivotCE
  10. #90  
    I can consistently get to this point. But it will never go further. I hear the Windows USB disconnect sound when it says "resetting phone". And then I heard the reconnect sound but it never comes back. At this point I can disconnect the phone from USB and I heard the disconnect sound and when I plug it in, it takes a while, but I hear the reconnect sound. Refreshing Device manager gets me "unknown usb device (device descriptor request failed). But the phone never comes back to...I don't know...I guess finish this flashing process in QPST.

    I'm sitting at that result with device manager right now. Looking at QPST I see that it finally errored out with "software download aborted". I'm going to leave the phone plugged in and reboot into Ubuntu.
    Attached Images Attached Images
    Follow me on Twitter
    For the latest webOS news check out pivotCE
  11. #91  
    No dice on Ubuntu. It's not able to get a device descriptor just like windows. You can see that from my earlier log I copied too. Just for added detail, pulling the battery and popping in a charged one to make sure it's not a battery problem has yielded two interesting things. 1. The phone goes back to qdload mode and 2. the proximity sensor lit up red. It's the weirdest thing. It is visibly red.

    Normally when I've run qpst I have normally left partition, dbl, fsbl, osbl, and amss.mbn checked. This time I unchecked everything but partition. Same result sadly. I believe qpst is trying to get the phone into diagnostic mode but to no avail. I could be wrong and I don't know that it's important. Looks like all the folks that were interested in this thread have moved on! Oh no! Help?
    Last edited by Alan Morford; 11/04/2014 at 08:15 PM.
    Follow me on Twitter
    For the latest webOS news check out pivotCE
  12. #92  
    How to reload webOS on TouchPad with LuneOS and CM10

    has anyone having a bricked pre3, tried this -auto way of doctoring ? (just to try all possibilities)
  13. #93  
    Quote Originally Posted by mazzinia View Post
    How to reload webOS on TouchPad with LuneOS and CM10

    has anyone having a bricked pre3, tried this -auto way of doctoring ? (just to try all possibilities)
    Unfortunately, that's a solution to a different problem. The 2nd and 3rd stage bootloader has to work before the Doctor will be able to do anything.

    "QHUSB-DLOAD mode" is a state where the Qualcomm SoC (Snapdragon-series in this case) is waiting for a firmware and/or bootloader reflash, and won't do anything until that's satisfied. It's a "blank slate" behavior and QPST, the tool used in reflashing the device isn't always getting the job done because the device has to reboot in between steps, and when it's rebooted it isn't seen by computer.

    I guess reflashing chips over JTAG is a more "foolproof" way of doing this, but it's even less fun because the pins you need to connect to are most likely obscured by the RF shielding on the board.


    Anyway... your suggestion, the "-auto" flag with the earliest OS version possible, that's for wiping and redrawing the partition table. Useful when the partition table is corrupted by an OS crash or Android install error.

    For a corrupted bootloader resulting in a "bricked" Touchpad, there's "rootzwiki TPdebrick"
    Last edited by Remy X; 11/15/2014 at 02:18 PM.
    ...
  14. #94  
    Thanks for the explanation
    Remy X likes this.
  15. #95  
    Quote Originally Posted by Remy X View Post
    For a corrupted bootloader resulting in a "bricked" Touchpad, there's "rootzwiki TPdebrick"
    Yes, for TP there is TPdebrick - but this discussion is about Pre3. How to resolve this issue on a Pre3. Still waiting for ideas/help ..
  16. #96  
    Quote Originally Posted by MartinH@webos View Post
    Yes, for TP there is TPdebrick - but this discussion is about Pre3. How to resolve this issue on a Pre3. Still waiting for ideas/help ..
    No need to police the thread

    I'm just giving a fuller explanation so that next time, we could avoid unintentional "disinformation"


    . . .

    However, for the Pre3, we are sort of poking around in the dark, unless we see what's being sent back and forth over USB. Debugging a USB data stream is outside my expertise, but i know enough to see that the Pre3 isn't sending a "greeting" for each of its "USB devices" that require drivers, and neither Windows' implementation of UPnP nor Ubuntu's sees it properly. If we could somehow bypass the "show and tell" process and talk directly, this reflash process could work.

    Have a look at this, just for inspiration: http://dangerousprototypes.com/2011/...-usb-analyzer/
    Last edited by Remy X; 11/15/2014 at 03:05 PM.
    ...
  17. #97  
    I know this is a Pre 3 thread, and an old one at that, but a lot of the potential links regarding this issue no longer work. I tried this process on my dead Touchpad between this thread and some comments from Top Tongue Barry on another one but I am getting Image download failed Cookie (if present) not received error. Anyone seen this or if so, if you were able to get around it.

    BTW, this was not an issue that TPDebrick would fix as I tried that route but boot is corrupted so it needs to be reflashed if possible.
Page 5 of 5 FirstFirst 12345

Posting Permissions