WNYConsoles
Troll Eating Dogs
Yes I understand that, but was anything changed that possibly prevents patching or some other RGH block, or is that information not available yet?
As stated in the OP,Yes I understand that, but was anything changed that possibly prevents patching or some other RGH block, or is that information not available yet?
Released: June 12, 2012
Known Changes:
Unpublished Changes:
- Avatar store added to social on the dashboard
- Updates to the avatar store
- Adds "Manage Exercise Info" to players Profile
- Sky is removed from the dashboard (now only accessible through the apps menu)
- Improvements and preparation for future Xbox live Enhancements
- CB has Changed
- RC4 Keystream Calc Has Changed
Warning
AS ALWAYS - DO NOT UPDATE WITHOUT HAVING FIRST DONE A FULL NAND DUMP AND CORRECT CPU KEY !
To many cooks spoil the broth springs to mind. Reading this is pricelessNew CB = need new patches for RGH
that's the way it is
To many cooks spoil the broth springs to mind. Reading this is priceless
Sent from my GT-I9100 using Tapatalk 2
Yea... they need to just make an announcement to clarify..
that the update does NOT effect Dual NAND
That the new update MUST be revered engineered before the RGH (2.0) glitch can continue to be used against it...
And that Any NAND you have you must increment the LDV before you may boot it...
hear hearJeezzuuzz... This thread does my head in! We are, what, less than 24 hours since the update went wild, and I have read so many "Does this mean we can't...?" and "Should I update...?" This can be summed up in the following expression... WTF!!!!, STFD and STFU... in that order.
From what I can tell, the rules have not changed one iota. Learn some freakin patience.
1. Hold off. Why not... There are no games that require that you use 15572 this very minute.
2. If you really want to play online with a modded drive then just do what has pretty much always been the case - Revert to stock before upgrade. The answer to the question "Will I get banned if I don't revert to stock?" has not changed since "banhammer" days. Why the hell would anyone with more than 1 post against their name even think to ask it?
3. If you think you may want to glitch your console in the future - grab your CPU key now, before you upgrade so you stand the best chance (and why upgrade unless you need to?). This has also been standard advice for ages - certainly before 14719 came out... again, why would this change? And why would scene people be asking this?
4. There are no guarantees, ever. Just smile and be happy you didn't get a sh*tbox PS3.
I was kinda thinking what Ubergeek https://team-xecuter.com/forums/member.php?u=38963said sometime ago, if we already have our cpu key we are in ok shape. We just need to wait on fix but we can always glitch our systems.so what you are saying is that you don't understand the implications of a new CB, or what RGH entails
you are definitely right about the being able to RGH2 forever IF:I was kinda thinking what Ubergeek https://team-xecuter.com/forums/member.php?u=38963said sometime ago, if we already have our cpu key we are in ok shape. We just need to wait on fix but we can always glitch our systems.
Good deal, I am not in no hurry to get the latest dash update I can play all my games just fine the way it is.![]()
And this is why, correct? (Taken from the RGH2.0 announcement)you are definitely right about the being able to RGH2 forever IF:
1. you have CPU key
2. you have RGH2able NAND dump
Basically we can update to any dash we want, flash the glitch image back, and still glitch the vulnerable CB_A as there's no fuse checks saying "Hey, you updated to a new CB version, I'm not going to run"?In the slim boot chain the 2nd bootloader (CB) is split into two pieces. The first part simply starts encryption and loads the second part, which does fuse checks and all the things that the old single CB did. By glitching the first part (CBA), we take control of the system before the fuse checks occur and can patch them out.
It's amazing more people don't seem to realize this. The fact that crossing the threshold from 12625 or lower to 13614 or higher triggers the DVD drive reflash should tell anyone that updates can put your DVD drive into "vendor" mode, thus bypassing the stealth of CFW during normal use.The reason we advise flashing back to stock is not for the drive being flashed by MS, it's because there's always a chance they are reading the drive during the update and checking for CFW.
highlighted... that dont help us corona owners telling us to grab our CPU KEY before we upgrade our dashJeezzuuzz... This thread does my head in! We are, what, less than 24 hours since the update went wild, and I have read so many "Does this mean we can't...?" and "Should I update...?" This can be summed up in the following expression... WTF!!!!, STFD and STFU... in that order.
From what I can tell, the rules have not changed one iota. Learn some freakin patience.
1. Hold off. Why not... There are no games that require that you use 15572 this very minute.
2. If you really want to play online with a modded drive then just do what has pretty much always been the case - Revert to stock before upgrade. The answer to the question "Will I get banned if I don't revert to stock?" has not changed since "banhammer" days. Why the hell would anyone with more than 1 post against their name even think to ask it?
3. If you think you may want to glitch your console in the future - grab your CPU key now, before you upgrade so you stand the best chance (and why upgrade unless you need to?). This has also been standard advice for ages - certainly before 14719 came out... again, why would this change? And why would scene people be asking this?
4. There are no guarantees, ever. Just smile and be happy you didn't get a sh*tbox PS3.
its just as important to save a rgh2able nand dump as your cpu keyhighlighted... that dont help us corona owners telling us to grab our CPU KEY before we upgrade our dash![]()
is is public yet to dump nand and get CPU of the corona ? hmmmmmits just as important to save a rgh2able nand dump as your cpu key
its easier for the end user to remember to just have a rgh2able nand (which contains your old CB_B) and your CPU keyI just glitched a Jasper 256mb after the 15572 update, with only a dump of its 14719_CB_B. I don't know why everyone is staying to get the CPU Key before you update. There is no need as long as you have a copy of the old CB_B so you can get the KeyStream, so you can encrypt your custom CB_B for the glitch. Also that is only untill we work out what they did to the RC4 encryption
In my opinion if you don't know how sh*t works dont use it. If you dont know how RGH works dont do it.its easier for the end user to remember to just have a rgh2able nand (which contains your old CB_B) and your CPU key
of course, you can re-create the keystream with just a cpukey and using a donor decrypted cb_b