Post: Free ConsoleID + How to Apply
Options
01-11-2013, 02:24 PM
#1
Sonoro
I like anteaters
As you know, ps_unban tool actually does changes in lv2, but when restarting the system it actually resets it back. So you will have to run the homebrew each time you boot your ps3.
Here it is:
[URL="https://pastie.org/private/ubmazjyc5svlgu7ydokmbq"]Click Here[/URL]
How to use
So, you can simply add it to PS_Unban package (by 0x00) doing the next steps:
-Unpack Ps_unban's pkg using pkgview or pkg toolkit (You must login or register to view this content.)
-Unself the EBOOT.BIN file inside USRDIR , using scetool (in cmd: scetool -d EBOOT.BIN EBOOT.ELF)
-Open the EBOOT.ELF file in You must login or register to view this content. and go to offset: 0x1AA8B0 and paste write (ctrl+b) firsts 16 numbers of the console id.
-In HxD, go to offset 0x1AA898 and paste write (ctrl+b) the remaining part of the consoleid.
-Save your EBOOT and self it back, then pack the pkg.
All credits for Ps_unban go to 0x00
Last edited by
Sonoro ; 01-11-2013 at 05:03 PM.
The following 17 users say thank you to Sonoro for this useful post:
The following user groaned Sonoro for this awful post:
01-13-2013, 01:42 AM
#20
BadChoicesZ
I defeated!
Originally posted by DEREKTROTTER
if you have trouble doing that, simply replace the eboot of the current homebrew app by FTP
I Actualy Tried That And Had No Luck, What I ended Up Doing Was Re-Creating The Eboot With Pkg ToolKit Gui And Then I Copied 0 byte package.conf file into the package aswell, and edited param.sfo ( doubt i needed to ) and set console id to other packages ( through option 6 in anscestor ) ... however Thanks anyways
, if any1 else is having this problem try this way to fixAlso mayb thats why when i just used ftp and replaced the eboot.bin it didnt work eitehr cause i think the first way i was encrypting it wasnt correct
01-13-2013, 03:58 PM
#22
wtfletmesignup
Keeper
Im having trouble getting the elf back to a bin file... keep getting "please specify a file type"
scetool -e EBOOT.ELF EBOOT.BIN
Im I doing that right?
edit: nvm i just used another tool
scetool -e EBOOT.ELF EBOOT.BIN
Im I doing that right?
edit: nvm i just used another tool
Last edited by
wtfletmesignup ; 01-13-2013 at 04:12 PM.
01-15-2013, 10:13 PM
#24
sarracen
Do a barrel roll!
Originally posted by DEREKTROTTER
if you have trouble doing that, simply replace the eboot of the current homebrew app by FTP
sup derek wondering if you can push me in the right direction ? im unable to open the scetool no matter what ive tried like 3days now its done my head totally in.i run cmd then write scetool -d EBOOT.BIN EBOOT.ELF with the response "scetool is not recognised as an internal or external command".i managed to find a scetool gui but when i try to decrypt eboot.bin it says error "could not decrypt header".would appreciate sum help bro.:confused:
01-15-2013, 10:15 PM
#25
DEREKTROTTER
You're Goddamn Right
01-15-2013, 10:43 PM
#26
sarracen
Do a barrel roll!
Originally posted by DEREKTROTTER
put this into a .bat file, same folder as scetool and run it
scetool.exe -v --decrypt EBOOT.BIN EBOOT.elf
just tried it still same thing cmd box says same thing and scetool gui still says could not decrypt header...
im running windows 7 64bit could this be the problem as ive read scetool was made for 32bit.ive tried running it in compatibilty mode with XP sp3 still nothing.
Last edited by
sarracen ; 01-15-2013 at 10:48 PM.
01-15-2013, 11:01 PM
#27
DEREKTROTTER
You're Goddamn Right
Originally posted by sarracen
just tried it still same thing cmd box says same thing and scetool gui still says could not decrypt header...
im running windows 7 64bit could this be the problem as ive read scetool was made for 32bit.ive tried running it in compatibilty mode with XP sp3 still nothing.
im running windows 7 64bit could this be the problem as ive read scetool was made for 32bit.ive tried running it in compatibilty mode with XP sp3 still nothing.
you need to update your keys then, it cant decrypt because the keys arent there.
The following user thanked DEREKTROTTER for this useful post:
Copyright © 2025, NextGenUpdate.
All Rights Reserved.
