Page 3 of 3 FirstFirst 123
Results 21 to 30 of 30

Thread: Unable to update firmware beyond P04

  1. #21
    Join Date
    Feb 2010
    Posts
    640

    Default

    try hwsetting-pbo-bootcode-18-5.bin in particular.

    -wigout

  2. #22
    Join Date
    Oct 2010
    Posts
    13

    Default

    Hi again. So I've been through all the HW Settings. No luck still. Getting the same error.

    I'm beginning to think it's beyond repair...

    I'd just like to mention that my usb cable has only 3 colors:

    Blue --> Rx, Red --> Tx, Orange --> GND

    as posted in if you scroll down:
    http://www.patriotmem.com/forums/showthread.php?t=3479

    No idea if it will make a difference in getting the 4 colour cable...

  3. #23
    Join Date
    Feb 2010
    Posts
    640

    Default

    If you are truly desperate, I'd probably end up trying exactly what volotova used- despite the fact that the bootcode and hw settings are for another player, at least we know that he had a modicum of success with the combo. The worst that can happen is, I think, that you'll be in the same situation you are now. The best that could happen would be a working Realtek Rom Monitor AND/OR Rescue kernel which should permit you try other/newer solutions for your problems.

    Anyway, if you're feeling that ambitious, I'm attaching those two files to this post. If you try them, let us know how it goes.

    I'm sorry I can't be of any more help at the moment,

    wigout
    Attached Files Attached Files

  4. #24
    Join Date
    Oct 2010
    Posts
    13

    Default

    Still no luck. I guess I will have to get a replacement media player. Too bad the PBO isnt available in New Zealand anymore

  5. #25
    Join Date
    Feb 2010
    Posts
    640

    Default

    One last possibility occurs to me:

    Many of the settings and artifacts inside the /dev/mtdblock/0 are relics- they apply to some sort of proto-version of the player.

    So perhaps the hwsetting bin that I recovered from the pbo has to do with the earliest bootcode from patriot- bootcode 16.

    So, one last thing: try the steps above, using the various hwsettings.bin that I supplied in post #20 with bootcode 16:
    1073_c0000_Deimos_avhdd_PATRIOT__PCMPBO25_128x1_pa l_rsq.0000.0202.0016.bin.zip

    Let us know what happens.

    Again, sorry for all the trouble,

    wigout

  6. #26
    Join Date
    Feb 2010
    Posts
    640

    Default

    Quote Originally Posted by chivyboy View Post
    OK... so I tried the resetting of the Bootcode but think I've hit a major wall. It won't boot up now and when I connect it to the PC it just says:

    ?hello world!
    s/d/g/c>
    And by the way, can you supply more details of how this happened? What files were you using, what technique, what you saw on the screen, any errors that you saw.

    (And if you have a log that would be great to see).

    -wigout

  7. #27
    Join Date
    Feb 2010
    Posts
    640

    Default

    Alright, one more thing to try:

    I examined the bootcode-18.bin and found what looked like the hwsetting.bin within that file.

    I have extracted that file and I am attaching it to this post.

    Try everything all over again, using the this file attached to this post plus the bootcode.18.bin.

    Let us know what happens,
    wigout

  8. #28
    Join Date
    Oct 2010
    Posts
    13

    Default

    Hey sorry I havent been checking the post lately as I thought all was lost. I will try these out over the next few days. Will let you know.

    Not sure how it all started. When I first got the device I flashed it to P04 which was fine. Later I tried P05 but it would never flash successfully, it would continue to boot over and over.
    I have several friends that have the PBO and updates have been working fine for them. I decided to take it to the next step and reflash the bootcode, thats then it all started I guess. Managed to connect in via serial ok but the first attempt to flash failed i think and has been like this ever since.

    I really appreciated the support you have been able to provide!

  9. #29
    Join Date
    Feb 2010
    Posts
    640

    Default

    Studying the hwsetting.bin that are out there in the GPL sourcecode releases & the package_MP.upg files, I believe you can extract the hwsetting bin from a bootcode file.

    (Note that I am doing this on a ubuntu 10.04 install, having compiled xxd from source: ftp://ftp.uni-erlangen.de/pub/utilit...xd-1.10.tar.gz because it has a help file I can understand and can reverse hexdumps and other cool things)

    Here's my example, using the pbo's bootcode 18 ( http://www.patriotmem.com/forums/att...1&d=1273528323 ):

    Code:
    find start of hwsetting bin
    xxd -c 4 1073_c0000_Deimos_avhdd_P020P01_PAL_128x1_pal_rsq.0000.0202.0018.bin | grep '1800 00b8' | cut -d ':' -f 1 | head -n 1
    000c1dc
    
    find start of end of hwsetting bin:
    xxd -c 4 -s 0x000c1dc 1073_c0000_Deimos_avhdd_P020P01_PAL_128x1_pal_rsq.0000.0202.0018.bin | grep 'ffff ffff' | head -n 1 | cut -d ':' -f 1
    000c5c4
    
    true end offset:
    echo "$((0x00c5c4)) + 4" | bc -l
    50632
    
    length of hwsetting:
    echo "50632 - $((0x000c1dc))" | bc -l
    1004
    
    output the hwsetting.bin:
    dd if=1073_c0000_Deimos_avhdd_P020P01_PAL_128x1_pal_rsq.0000.0202.0018.bin bs=1 skip=$((0x000c1dc)) count=1004 of=hwsetting.bin
    Just for the record.

    It would be great if someone with an already bricked machine, like chivyboy, would try this method out.

    -wigout

  10. #30
    Join Date
    Oct 2010
    Posts
    13

    Default

    Sorry for the long wait.... Once again still no luck

    All can't be lost if I am able to get s/d/g/c> to show up right?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •