Bypass method theory

[RootedSys]

So I don't want to risk my ps3 but maybe someone else does...anyways their a version.txt that contains your ps3 firmware number if you change it to 3.42 then you trick your ps3 in thinking its 3.42 and then it passes sony's check

/dev_flash/vsh/etc/version.txt

release:03.4100:
build:45039,20100721:tetsu@tetsu-linux22.rd.scei.sony.co.jp
target:0001:CEX-ww
security:3960@security/sdk_branches/release_341/trunk:
system:45857@sys/sdk_branches/release_341/trunk:
x3:15557@x3/branches/target34x:
paf:6082@paf/branches/target34x:
vsh:82665@vsh/branches/target34x:
sys_jp:67@sys_jp/branches/target34x:
ps1emu:6377@emu/branches/target101/ps1:
ps1netemu:6520@emu/branches/target340/ps1_net:
ps1newemu:6378@emu/branches/target202/ps1_new:
ps2emu:6448@emu/branches/target340/ps2:
ps2gxemu:13784@branches/target340/gx:
ps2softemu:13474@branches/soft190/soft:
pspemu:6501@emu/branches/target340/psp:
emerald:3697@emerald/target34x:
bdp:13407@bdp/branches/target34x:
patch::
auth:45039:

[ithildin]

Humm that could work. Unfortunately the PS3 FTP server can't write to dev_flash, at least not yet. Otherwise it would be worth a try!

[Simon66]

Humm that could work. Unfortunately the PS3 FTP server can't write to dev_flash, at least not yet. Otherwise it would be worth a try!

Ye I tried changing it but it wont let me. I get this

Error: Critical file transfer error

[SP193]

So I don't want to risk my ps3 but maybe someone else does...anyways their a version.txt that contains your ps3 firmware number if you change it to 3.42 then you trick your ps3 in thinking its 3.42 and then it passes sony's check

/dev_flash/vsh/etc/version.txt

Hmm... looks like what PSP CFWs have. They have an option to use an external "version.txt" instead of the one inside the PSP's NAND flash chip.

It did trick some games and programs... but Sony did manage to block users of such CFWs from the PSN. This suggests that Sony can detect the real firmware version/or the existance of a CFW....

[Dorksk8tr3]

I was looking at that same thing just a while ago. There is also this information in your LV2.bin if you dump it.

Notice there is a website to call and test. We could maybe jsut block this site in the router and it will not be able to call to test.

There is another problem. I noticed I get that nag to update when I connect the network only. If I never connect it it doesn't pop up. Then as soon as I connect the network (using a physical switch on a 4 way hub) it pops up. Way to fast to be connecting. The nag must be stored on the system and is called or checked when the network is enables.

We could block the site and locate the nag> I am pretty sure the nag is in the LV2.

I will let you know what I find out.

Edit:
This is from the LV2.bin

Version: 0x%08x.
Revision: %d.
System Software Version: 0x00%1d%1d%1d000....
Game Application Title ID: %s........./dev_hdd1/crash_report/kernel/ps3crash-kernel.dat.tmp...

/dev_hdd1/crash_report/kernel/ps3crash-kernel.dat.......
/dev_hdd1/crash_report../dev_hdd1/crash_report/kernel...
PlayStation(R)3.Debugging Station.......
Reference Tool..Unknown.@...............................vsh. self........ ........................