Page 4 of 5 FirstFirst 12345 LastLast
Results 61 to 80 of 97
Like Tree19Likes
  1. #61  
    To bring this thread up.... I have a bricked Pre3 in QDLOAD-Mode.

    So far I see the following options:
    - omap3_usbload
    - QPST with the proper files
    - QPST backup / restore with a 2nd working Pre3

    omap3_usbload
    I modified the omap3_usbload for the Pre3 Vendor and DeviceID and added two debug lines. (see attached patch file).
    Code:
    # ./usbload boot.bin 
    TI OMAP3 USB boot ROM tool, version 0.1
    (c) 2008 Martin Mueller <martinmm@pfump.org>
    
    .Vendor: 5c6 Device: 9008 
    
    found device!
    could not set configuration
    You can compile it on Ubuntu 64 Bits with
    Code:
    gcc omap3_usbload_pre3.c -o usbload -L/usr/lib/_64-linux-gnu/ -l usb
    But so far, no luck here


    QPST
    Anybody has a proper hex file? The other files I am able to get out of the doctor-file. Is it possible the create this file from a working Pre3?


    QPST backup/restore
    How do I put a working Pre3 in QDLOAD mode? Will it work at all?
    Attached Files Attached Files
  2. #62  
    Quote Originally Posted by nichtwirklich View Post
    To bring this thread up.... I have a bricked Pre3 in QDLOAD-Mode.

    So far I see the following options:
    - omap3_usbload
    - QPST with the proper files
    - QPST backup / restore with a 2nd working Pre3

    omap3_usbload
    I modified the omap3_usbload for the Pre3 Vendor and DeviceID and added two debug lines. (see attached patch file).
    Code:
    # ./usbload boot.bin 
    TI OMAP3 USB boot ROM tool, version 0.1
    (c) 2008 Martin Mueller <martinmm@pfump.org>
    
    .Vendor: 5c6 Device: 9008 
    
    found device!
    could not set configuration
    You can compile it on Ubuntu 64 Bits with
    Code:
    gcc omap3_usbload_pre3.c -o usbload -L/usr/lib/_64-linux-gnu/ -l usb
    But so far, no luck here


    QPST
    Anybody has a proper hex file? The other files I am able to get out of the doctor-file. Is it possible the create this file from a working Pre3?


    QPST backup/restore
    How do I put a working Pre3 in QDLOAD mode? Will it work at all?
    OMAP3 USB Load SHOULDN'T work because Pre3 is Qualcomm and not TI OMAP.

    Not sure how to get the HEX file. The guy @ XDA or Rootzwiki who fixed TP might know. Maybe TTB knows as well?

    I'm happy to extract it from 1 of my Pre3's when required....
  3. #63  
    Quote Originally Posted by Herrie View Post
    OMAP3 USB Load SHOULDN'T work because Pre3 is Qualcomm and not TI OMAP.
    Oh okay, I thought they are all Qualcomm, I just have 2 x Pre3, 1 x Veer and one TP. So my mistake

    Not sure how to get the HEX file. The guy @ XDA or Rootzwiki who fixed TP might know. Maybe TTB knows as well?

    I'm happy to extract it from 1 of my Pre3's when required....
    Thank you. I am waiting a few days, maybe somebody has it or know how.

    Better to extract it from my second Pre3, I think I also need the tokens, and the second Pre3 is without chassis so transferred tokens (SN/IMEI) would be okay for me. (I think I have a backup of the tokens anyway, because I converted it from US to EU)

    Oh I could swap the Pre3s of course, but the bricked Pre3 is a 16GB qwertZ model with Umlauts. The other is at the moment a 8GB qwertY. I prefer to have the 16GB model of course.
  4. #64  
    Hi guys

    I came some further:

    I foud the EMMCBLD.HEX file as 7x30 bootloader. I was able to programm the Pre3 with the QPST-Tool. I needed a few tries to remove appsloader and apps. But finally it was successful, it disconnected the phone and it appeared with the diag mode once. Now the QPST tool doesn't detect it anymore but my Linux machine sees a Qualcomm MMC storage with 16GB. the partition table is strange.

    For the moment I saved my phone with dd to a file, because on /media/internal were some importent pictures I hadn't backup before. I will get the pics later with a file scarving forensic tool.

    I am here now and no clue what to do...

    The USB ProductID switched from 9008 to 9006, this tells us what???

    Code:
    [1567744.325381] usb 2-1.8: new high-speed USB device number 112 using ehci_hcd
    [1567744.417867] usb 2-1.8: config 1 has an invalid interface number: 20 but max is 1
    [1567744.417870] usb 2-1.8: config 1 has no interface number 1
    [1567744.419631] scsi34 : usb-storage 2-1.8:1.20
    [1567744.557563] init: Handling usb-device-added event
    [1567744.558056] init: Handling usb-device-added event
    [1567744.558351] init: Handling scsi-device-added event
    [1567744.558667] init: Handling scsi_host-device-added event
    [1567744.695920] init: Handling usb-device-added event
    [1567745.418414] scsi 34:0:0:0: Direct-Access     Qualcomm MMC Storage      2.31 PQ: 0 ANSI: 2
    [1567745.419690] sd 34:0:0:0: Attached scsi generic sg3 type 0
    [1567745.420352] sd 34:0:0:0: [sdc] 31105024 512-byte logical blocks: (15.9 GB/14.8 GiB)
    [1567745.420399] init: Handling scsi-device-added event
    [1567745.420817] init: Handling scsi-device-added event
    [1567745.420831] sd 34:0:0:0: [sdc] Write Protect is off
    [1567745.420837] sd 34:0:0:0: [sdc] Mode Sense: 0f 0e 00 00
    [1567745.421359] sd 34:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [1567745.421879] init: Handling scsi_disk-device-added event
    [1567745.422039] init: Handling scsi_device-device-added event
    [1567745.422168] init: Handling bdi-device-added event
    [1567745.422325] init: Handling bsg-device-added event
    [1567745.422484] init: Handling scsi_generic-device-added event
    [1567745.426966]  sdc: sdc1 sdc2 sdc3 sdc4 < >
    [1567745.430077] sd 34:0:0:0: [sdc] Attached SCSI removable disk
    [1567745.663411] init: Handling block-device-added event
    Code:
    # fdisk /dev/sdc
    Warnung: Schreiben wird ungültiges Flag 0x0000 in Part.-tabelle 5 korrigieren
    
    Befehl (m für Hilfe): p
    
    Disk /dev/sdc: 15.9 GB, 15925772288 bytes
    1 Köpfe, 32 Sektoren/Spur, 972032 Zylinder, zusammen 31105024 Sektoren
    Einheiten = Sektoren von 1 × 512 = 512 Bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Festplattenidentifikation: 0x00000000
    
       Gerät  boot.     Anfang        Ende     Blöcke   Id  System
    /dev/sdc1               1      819200      409600    6  FAT16
    /dev/sdc2   *      819201      820200         500   4d  QNX4.x
    /dev/sdc3          820201      823200        1500   46  Unbekannt
    /dev/sdc4          823201     1823200      500000    5  Erweiterte
    Code:
    # lsusb | grep Qual
    Bus 002 Device 112: ID 05c6:9006 Qualcomm, Inc.
    The screen and led remains dark, no optical sign of living at all.
    Where I am now and what to do? Just copy the boot sector from my working Pre3 or the whole disk image?

    I am not sure about the copyright, of the emmcbld.hex, so I did not attach it....
    fxspec06 likes this.
  5. #65  
    HP Logo!!!!!!! The first one (BootLogo.tga)

    EDIT: Second boot (maybe fsck) the dark/bright logo ...

    EDIT2: UP AND RUNNING!!!!!

    The most apps are gone and so on, but this could be expected, I modified the LVM partitions so it doesn't fit with the layout of a fresh doctored phone.
    Last edited by nichtwirklich; 09/13/2013 at 07:57 AM.
  6. #66  
    Quote Originally Posted by nichtwirklich View Post
    HP Logo!!!!!!! The first one (BootLogo.tga)

    EDIT: Second boot (maybe fsck) the dark/bright logo ...

    EDIT2: UP AND RUNNING!!!!!

    The most apps are gone and so on, but this could be expected, I modified the LVM partitions so it doesn't fit with the layout of a fresh doctored phone.
    Awesome! Did you do anything besides what you have written down here? Still have to revive my Pre3.
  7. #67  
    i might be one of the next to attempt resurrection

    not prepared yet though.
    Neo Enyo 2.0 Twitter App: NOW AVAILABLE | WON REVIEW
    clearview - clear card app for HP TOUCHPAD
    Wild'n Video Poker - AVAILABLE FOR ALL WEBOS DEVICES! | follow for latest updates - @fxspec06

  8. #68  
    Quote Originally Posted by MikeDeWitt View Post
    Awesome! Did you do anything besides what you have written down here? Still have to revive my Pre3.
    I am short on time but a brief summary:

    - Read dwarfs post
    - Put all mbn files and the EMMCBLD.HEX file as 7x30 bootloader in one directory.
    - qpst tool -> multi image and select the partition mbn, with advanced you can enable disable the single mbn files (disable apps and appsloader)
    - flash phone
    - qpst tries to get the phone after it in diag mode, but it failed (for me)
    - connect phone to a linux machine, it is now in usb mass stroage mode
    - dd the partition table ( dd if=/youbackupofmbr.dd of=/dev/sdABCDE bs=1k count=1 (use the device of your cell phone, check with dmesg)
    - after this maybe your phone works already
    - if not same procedure to reach mass storage mode and now use dd to copy all partitions from a working pre3 to a non working pre3 (problem here is to get the partition without a second phone), be careful with your tokens (partition)... you cannot use the same tokens on two devices!!!! HP and your cell phone provider will kick your ***, if both phones are online at the same time!
    - after this reboot it should work, maybe you must boot twice for filesystem check run (reboots by itself)
    - from a working pre you reacht the mass torage mode by pressing "t" while powering up the device
    - If you modifed your lvm partition (e.g. ubuntu, optware) layout you must doctor the device, but in anyway after you copied your media doctor it, you are in a undefined state here

    Will post the mbr backup tomorrow, I assume a 1k partition table has no copyright

    for dd always sue bs=1k (blocksize = 1 kilobyte), get the counts out of the xml file in the doctor file.
  9. #69  
    Well...

    I have no idea how to get the MPRG7x30.hex file

    I do have extracted the .mbn files from the doctor.

    Also where has 7x30 to be inserted?
    Last edited by MikeDeWitt; 09/21/2013 at 05:29 AM.
  10. #70  
    Quote Originally Posted by MikeDeWitt View Post
    Well...

    I have no idea how to get the MPRG7x30.hex file

    I do have extracted the .mbn files from the doctor.

    Also where has 7x30 to be inserted?
    google for EMMCBLD.HEX, third hit (dev-host) -> https://www.google.de/#q=site%3Ad-h.st+EMMCBLD.HEX

    Just put this hex file and all the mbn files in one directory, QPST recognizes all the files by itself after you selected the partition.mbn.

    Oh DO NOT dd the p7, p8 and p13 partition if not needed.

    dd the partition table and then first backup all partition from the broken phone. So:

    1. Use QPST to get from Download to mass storage mode (Windows PC)
    2. In mass storage mode, dd the partition table from the working to the broken phone (Now Linux)
    3. backup at least p7, p8 and p13 (just backup all: p1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13 -p4 is the extend partition, not needed)
    3. Try to reboot, if it works, fine, doctor your device
    4. if not try to dd 1, 2, 3, 5, 6, 9, 11, 12, from the wokring to the broken
    5. reboot
    6. if not dd also 7, 8, 13 and be prepared for imei trouble
  11. #71  
    for MikeDeWitt
    Attached Images Attached Images
    terroar1776 likes this.
  12. #72  
    Quote Originally Posted by nichtwirklich View Post
    for MikeDeWitt
    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
  13. #73  
    Terroar,

    you almost made it! Actually from this point it should be easy to recover your phone (if the hardware is not broken).

    do you have a second pre 3 available?

    do you have a linux system installed?

    if you need linux get a live cd or usb image e.g. from ubuntu.
    if you don't have a second pre3, i will attach the boot sector of the pre 3 here.

    Drop me a PN when you answer inside the thread, I don't check the forum so often.
  14. #74  
    Quote Originally Posted by nichtwirklich View Post
    Terroar,

    you almost made it! Actually from this point it should be easy to recover your phone (if the hardware is not broken).

    do you have a second pre 3 available?

    do you have a linux system installed?

    if you need linux get a live cd or usb image e.g. from ubuntu.
    if you don't have a second pre3, i will attach the boot sector of the pre 3 here.

    Drop me a PN when you answer inside the thread, I don't check the forum so often.
    no second pre 3 here fam, I do have linux installed in my laptop though ... please attach the boot sector and also give me a run down of the next steps
  15. #75  
    I couldn't get it to work. Do get an endless amount of errors in the log file
  16. #76  
    Quote Originally Posted by terroar1776 View Post
    no second pre 3 here fam, I do have linux installed in my laptop though ... please attach the boot sector and also give me a run down of the next steps
    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.
    Attached Files Attached Files
  17. #77  
    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 ended up deleteing my work hard drive like this ... I dont know how to see whats my sdb ... a little more help would be appreciate
  18. #78  
    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.
    Hey fam, if possible do you think we can try this on teamviewer or something ... Im back to qload again after the hp-boot-secter ..... lol
  19. #79  
    Quote Originally Posted by terroar1776 View Post
    Hey fam, if possible do you think we can try this on teamviewer or something ... Im back to qload again after the hp-boot-secter ..... lol
    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.
  20. #80  
    I'm stuck with this:
    Quote Originally Posted by nichtwirklich View Post
    - Read dwarfs post
    - Put all mbn files and the EMMCBLD.HEX file as 7x30 bootloader in one directory.
    - qpst tool -> multi image and select the partition mbn, with advanced you can enable disable the single mbn files (disable apps and appsloader)
    - flash phone
    I suppose you were talking about this post: dadwarf: Working on ... HP Pre 3 stuck in Download Mode
    I put all the files in a folder:
    - amss.mbn
    - dbl.mbn
    - fsbl.mbn
    - osbl.mbn
    - partition.mbn
    - EMMCBLD.HEX
    Started the QPST tool and it recognized my phone on COM8.
    I've Started "Software download".
    I've chosen the "Multi-image" tab.
    I've selected the previously populated folder.
    I've selected the Boot system: "Sec Boot 2.0"
    I've set "Use Emerg. Host D/L" to true.
    When I click Start then it gives an error "Could Not Open Flash Programming File"

    What am I doing wrong? Anybody any thoughts?
Page 4 of 5 FirstFirst 12345 LastLast

Posting Permissions