Remember that IOSU doesn't need kernel to be exploited, so this is irrelevant.
You still run apps in the PPC kernel so its still quite relevant.
Remember that IOSU doesn't need kernel to be exploited, so this is irrelevant.
yeah, i'm the same guy. you're welcomeDon't be sorry, Lol. The progress report was much appreciated.
Also, thanks for the ps3 bluray drive emulation fix for ps3mfw, assuming you're the same zecoxao (I doubt there are others). I'm using it on my broken bluray ps3
But loadiine as it is now will soon be irrelevant after IOSU release, because USB backup loaders are way more convientent (and better) and will only use IOSU meaning kernel is not even needed for it.Uhmmm I think you didn't know what he meant, he was talking about kernel addresses used for example in Loadiine v4, at least one of them was changed in 5.4.0 hence we couldn't make that version of Loadiine work that time.
It's not about access level, it's about addresses that we were using before that now are being used by some app by default.
Right after I purchased my 128GB SD Card :'(But loadiine as it is now will soon be irrelevant after IOSU release, because USB backup loaders are way more convientent (and better) and will only use IOSU meaning kernel is not even needed for it.
But loadiine as it is now will soon be irrelevant after IOSU release, because USB backup loaders are way more convientent (and better) and will only use IOSU meaning kernel is not even needed for it.
Its ok, great to kniw that the only thing needed is obfuscationnope. sorry
I'm really confused..how are you going to play your backups without a kernel?
Out of curiosity, what would the developer keys do for you?5.3.2 is also being worked on because some people have devkits on that version so, naturally, we want the dev keys
Then someone can reobfuscate it after it's deobfuscated.I bet that in less than 2 or 3 weeks the IOSU kernel exploit will be deobfuscated by someone again like they did with the WUP Installer
Uh... What's the point when we then know how it works o-Ó?Then someone can reobfuscate it after it's deobfuscated.
I don't know, I obfuscate stuff all the time. That's why i failed my java class, teacher didn't know what the hell he was looking at. I'm not going to let him get rich off my GUI calculator though. Screw that.Uh... What's the point when we then know how it works o-Ó?
Maybe, just maybe you shouldn't obfuscate all the things XDI don't know, I obfuscate stuff all the time. That's why i failed my java class, teacher didn't know what the hell he was looking at. I'm not going to let him get rich off my GUI calculator though. Screw that.
You made my dayI don't know, I obfuscate stuff all the time. That's why i failed my java class, teacher didn't know what the hell he was looking at. I'm not going to let him get rich off my GUI calculator though. Screw that.
firmware with symbols.Out of curiosity, what would the developer keys do for you?
Do I update to 5.5.1 or not, since i'm on an obscure firmware (5.3.0) and the exploit needs porting.
I think that is one of the reason they are waiting for to reléase it, jejeje, meaby we should talk more and more, meaby they need to feel more popular.Whoa, give it 2 weeks and this thread will already reach the 1,000 page mark.
Impressive O.OWhoa, give it 2 weeks and this thread will already reach the 1,000 page mark.