Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Ran a PSP 2.80 eboot Updater Renamed To 3.00 With Hex Editor

                  
   
  1. #1

    Default Ran a PSP 2.80 eboot Updater Renamed To 3.00 With Hex Editor

    Not To Sound any n00bish but
    i ran 2.80 update i changed everything in the eboot
    to 3.00 and it worked i got version 3.00
    i did it on a psp 2.80 ta-082 motherboard
    i was mad for a second but it worked
    it didn't say The File Was corrupted or anything
    my psp version is 3.00 i changed it everything from 2.80 is still on it

  2. #2
    DCEmu Legend Video_freak's Avatar
    Join Date
    Dec 2005
    Location
    Bay Area, California
    Posts
    2,892
    Rep Power
    107

    Default

    Good for you! You'll need some proof however...

  3. #3

    Default

    but how i don't have a web cam or digital camera
    and i certainly don't want anyone with 2.80 to brick their psp's is there any other way

  4. #4

    Default

    ima work on it a bit to see what else i can do

  5. #5
    PSP Flash Coder IndianCheese's Avatar
    Join Date
    Jul 2005
    Location
    The Burgh, PA 'n at
    Age
    33
    Posts
    1,106
    Rep Power
    81

    Default

    Well, in any way, you are SCREWED. If you are lying, it's not true (imagine that). If you are telling the truth, you won't be able to update to 2.90 when it comes out.

    But if you are telling the truth, please PM me the EBOOT.PBP file. I will not update my 2.80, but I just want to see if it actually successfully boots the update file.
    You don't need to know my mental status. You probably don't want to, either.

    September 5th, 2005:
    Quote Originally Posted by F34R
    There wont be a N64 emu on the PSP. Not one that is playable anyways.
    Need LocationFree help? Send me a PM!


  6. #6
    DCEmu Old Pro SSaxdude's Avatar
    Join Date
    Dec 2005
    Location
    Suburbia, IL
    Posts
    1,928
    Rep Power
    82

    Default

    Well then maybe he could hex edit the 2.9 update to 3.01 or something. This has been done before but it won't lead to anything good (like a downgrader.)

  7. #7
    DCEmu Old Pro M!ckeY's Avatar
    Join Date
    Mar 2006
    Age
    36
    Posts
    1,100
    Rep Power
    74

    Default

    yeah, all you do is change the version number

    also, he should have changed it to 1.00 then have tried a 1.50 update >.>

  8. #8
    DCEmu Legend Accordion's Avatar
    Join Date
    Jan 2006
    Location
    Birmingham, UK
    Age
    36
    Posts
    2,884
    Rep Power
    90

    Default

    Quote Originally Posted by motoko250
    yeah, all you do is change the version number

    also, he should have changed it to 1.00 then have tried a 1.50 update >.>
    that would brick the ta-82

    even if it worked, there is no point

  9. #9
    DCEmu Regular psiko_scweek's Avatar
    Join Date
    Apr 2006
    Posts
    315
    Rep Power
    71

    Default

    this is obviously fake. No offense but the eboots for the updates are encrypted. By hex editing the eboot it would break the encrpytion and render the eboot unusable.

  10. #10
    DCEmu Legend
    Join Date
    Sep 2005
    Posts
    2,355
    Rep Power
    82

    Default

    Quote Originally Posted by motoko250
    yeah, all you do is change the version number

    also, he should have changed it to 1.00 then have tried a 1.50 update >.>
    Not to mention the PSP would know that the version # is older than the source of the 'update'. Can't take a 2.8 PSP and update it with an eboot that thinks its a 1.0. In fact, I doubt this even worked at all.

    In all my tests ( that I did last year, when Swaploit just came out) I took an eboot, hexed it and tried it, didn't load. I had to use a newer eboot to get the update started then swapped the memsticks to the one that had the hexed 1.5 update on it. The PSP knows when the source is older than whats in flash and stopped the update anyway.

    So its impossible to 'update' with a hexed eboot, first and foremost and secondly its impossible to even get it working, since the PSP checks the files in the eboot (I guess they have some markers in the actually update file that says the real version) against its internal version number.

    The only reason the downgraders work is because they change in the internal version number of the PSP to 1.0, so then you apply the 1.5 update and voila, it works great.

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Bookmarks

Posting Permissions

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