Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Random Modding Thoughts...
Comments
-
-
c0z's Dashlaunch v2.20 v2.21 is out for the 12625 kernel - works like a charm, savage stuff to autoload FSD. It's also got a LIVE blocker that routes LIVE traffic to loopback (the console itself) - definitely a worthy addition
fbBuild v0.2 is out and it's got a good few additions to it but it's a bit tricky to get working. It can now generate 3 kernels (9199, 12611 and 12625) and each one has their own folder. The chosen folder can be done by using a command line switch (e.g. -f 9199). The problem is that it seems to be distributed without the core kernel files now (e.g. bootanim.xex, etc) so I'm not sure where you're supposed to get them from. I tried taking them from my original nand but I was missing a few so I gave up and downloaded a version from SevenSins that has all the kernel files for the 3 dashboards in it already :P
Once again, follow instructions on Page 3 of the JTAG thread until BestPig comes with an update
0 -
-
-
-
Advertisement
-
-
-
-
-
I warn you guys, nobody listens
1. Download this file which is fbbuild v0.20 with the dashboard files already loaded (can generate 12625, 12611 and 9199 dashboards). Extract to a folder e.g. C:\fbbuild
2. Download the SMC files I uploaded here. Extract the SMC file for your console model to C:\fbbuild\mydata and rename it to smc.bin
3. Open 360 Flash tool (v0.97 minimum) and click Settings->Options and tick the box that says "Extract ibuild compatible files". Then open your nand dump (original, current, any dump will do) and click extract on the bottom. Tick the box for 'config blocks' and 'Keyvault' and click OK. Choose a folder for these files. When extraction is done, go to that folder and there'll be a folder called freeBOOT, click iit, then into data and you will find two files - kv.bin and smc_config.bin. Copy these two files to C:\fbBuild\mydata
4. Edit C:\fbbuild\mydata\cpukey.txt to have your CPU key on the first line, not the dummy key of the console.
5. Ensure that C:\fbbuild\1blkey.txt has the right 1blkey (same for all consoles) of DD88AD0C9ED669E7B56794FB68563EFA
6. Open command prompt, go to c:\fbbuild and type the following:fbbuild -d mydata -f 12625 -c jasper512 C:\updflash.bin
-d is the folder where your console data is
-f is the folder where the kernel data is, if not specified it will use folder called 'data' in fbbuild folder
-c is the model - falcon, opus, zephyr, falcon256, falcon512 etc
If you want more info on the build use -v or for a full list of options type fbbuild with no arguments.
It will generate C:\updflash.bin, copy to USB stick, update with Xellous or Flash360. This method has never failed me, I have built updflash.bin files for guys and given them the link over the net, no trouble at all once I have their model, CPUkey, kv and smc_config. Coolshrimp, EZ JTAG tool and everything not Bestpig is ropey as hell, I refuse to use them. They are just a UI around this tool, DIY is best 0 -
Advertisement
-
-
-
If I'd known you'd run into problems with coolshrimp I wouldn't have recommended it was just talking from my own experience, should be easy enough to recover from
Not your fault at all, I'd forgotten you mentioned it completely & stumbled across it myself this morning. Serious, serious pain in the ar$e now. Can't get the usb pic tool recognised, apparently the drivers are in the nandpro folder but Win 7 x64 won't install them ("Doesn't contain compatible driver...make sure its designed to work with 64 bit blah blah")0 -
-
-
-
-
-
-
-
Advertisement
-
-
-
-
Bestpig won't update his tool, I don't think he has any interest. It's been over a month since 12625 was out. And seriously, 6 steps is not that hard - your problem was with the fact you wrecked your nand to start with
The reason you could only get an encrypted keyvault was because you didn't have the CPU key right, correct?0 -
TouchingVirus wrote: »Bestpig won't update his tool, I don't think he has any interest. It's been over a month since 12625 was out. And seriously, 6 steps is not that hard - your problem was with the fact you wrecked your nand to start with
The reason you could only get an encrypted keyvault was because you didn't have the CPU key right, correct?
Em not entirely, I had to input my cpu key into the programme & save it. Once that was done everything else went smoothly. I only wrecked my nand through lazyness, a mistake I will not repeat again - the fbbuild way is the way forward assuming BP is finished.
Seriously though, how could the coolshrimp tool have messed up my nand so much. It's not as if I don't understand any of the switches/variables & everything was double checked to prevent happening what actually hapened. I'm glad its over just, from the minute I got no Xell I knew my day was written off :mad:0 -
Em not entirely, I had to input my cpu key into the programme & save it. Once that was done everything else went smoothly. I only wrecked my nand through lazyness, a mistake I will not repeat again - the fbbuild way is the way forward assuming BP is finished.
Seriously though, how could the coolshrimp tool have messed up my nand so much. It's not as if I don't understand any of the switches/variables & everything was double checked to prevent happening what actually hapened. I'm glad its over just, from the minute I got no Xell I knew my day was written off :mad:
No idea how it manages to mess things up, I think it's when it goes writing the KV it messes up and that will prevent Xell/freeBOOT from running. I don't know how that tool works, I just know that when I tried to use it on 3 separate times it wrecked things and I had to go soldering, so now I avoid it like the plague
And yeah, you need a decrypted KV for all the methods which is why you have to supply your CPU key. So in order to decrypt the KV you have to save your CPU key in 360 Flash tool. That tool is epic by the way, I love it 0 -
-
-
-
Advertisement
-
- New LiteOn drive out for the slim drives 
Advertisement