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
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back from 1 to 10+ pages to re-sync the thread and this will then show the latest posts. Thanks, Mike.
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest
So you want to JTAG your xbox360? (POST 248 FOR xeBuild/16197 TUT)
Comments
-
-
Ok lads I think this might warrant a thread of its own, so as not to try & dilute the content of this particular thread (which is essentially the jtag process & directly related issues). So Helix if your not sorted already, I'll ask you to create a new thread for the Kinect issue if thats ok
0 -
-
-
-
Advertisement
-
TouchingVirus wrote: »If you read the first post you'd know the answer
Thanks just read through it there no hope of jtag my xbox
Thats my PS3 & Xbox that i can't do anything with0 -
-
-
-
-
Advertisement
-
Every nand has a reserved area of 32 blocks at the very end of the reserved (system) part of the nand which is for bad-block remapping.
On a 16MB nand the first bad block encountered should be moved to 0x3FF, the second should be moved to 0x3FE and so on. Say I get a bad block error on block 0x43 (within the first 50 blocks which is vital for XeLL) then I would do the following:nandpro <xellous.bin>: -r16 block0x43.bin 43 1 nandpro usb: -w16 block0x43.bin 3FF 1
It might also be an idea if that doesn't work to erase the bad block like so:nandpro usb: -e16 43 1
Now block 0x43 is located at 0x3FF. If you encountered another bad block later you do the same thing but remap to 0x3FE ..then 0x3FD and so on. If you get more than 32 bad blocks the nand is wrecked but I'd check my soldering first, 32 bad blocks is a lot :P
On 256/512MB Jaspers it's a little different. Nandpro reads blocksizes in 16KB no matter what nand it's reading, but Big Block nands have a blocksize of 128KB. This is why when you type "nandpro usb: -r16 kv.bin 1 1" on a Big Block nand nandpro will read 8 blocks (8x16KB = 128KB, or 1 big block).
So on a 256/512MB nand, when you read one bad block you'll get 8 errors, one for each 16KB mini-read). The remapping space takes place at 0xFFF on BB nands, but since you're writing 8 locations there's some tweaking involved. Let's run an example. Reading a BB nand and there's an error on block 0x1D0-0x1D7 (1 big block). Then to move this block you do the following:nandpro <nand_file_to_write.bin>: -r256 1D0 8 nandpro usb: -w256 FF8 8
You read the 8 blocks (1 big block), 128KB bin file from the file you want to write. Then you write it to the reserved bad block area starting at 0xFFF - (#number of bad blocks to date * 8) - 8. So on the first bad block that's 0xFFF - 8 which is 0xFF8. On the second it's 0xFFF - 8 - 8 which is 0xFF0, with a 3rd bad block you're down to 0xFFF-16-8 which is 0xFE8 and so on.
You can also attempt to erase the bad block using the -e switch and see if that helps too. Once again, more than 32 blocks and you've got a real issue 0 -
-
-
-
-
Build Instructions (Updated for latest fbBuild v0.33):
For simplicity you need the following:
1) Your CPU Key
2) A copy of your nand (original or FreeBOOT) and SMC
3) Dashboard Data (Google for "xxxxx Dashboard data" where XXXXX is the version number e.g. 12611, 13599. Here is 13604
4) fbBuild v0.33 (xbins -> /XBOX 360/development/fbBuild/)
Getting ready
Download fbBuild and extract it to a folder - say C:\fbBuild
Open your dashboard data zip file and extract the contents to C:\fbBuild\<version_number> e.g. for 13604.zip, extract the contents to C:\fbBuild\13604. The folder should already exist in C:\fbBuild anyway.
Edit C:\fbBuild\1blkey.txt. On the first line is a dummy key - replace it with DD88AD0C9ED669E7B56794FB68563EFA
Edit C:\fbBuild\mydata\cpukey.txt. On the first line is a dummy key - replace it with the CPU key of the console.
Extracting KV and SMC_CONFIG.bin
Open up 360 Flash Tool v0.97 and click Settings->Options. Tick the box that says "Extract ibuild compatible files". Then open your nand 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 into it, then into data and you will find two files - kv.bin and smc_config.bin. Copy these two files to C:\fbBuild\mydata.
Picking the right SMC (not for Xenon consoles)
This step is very important if your console is not a xenon - flashing the wrong SMC can end your JTAG
If the nand file you used to extract the KV.bin and SMC_CONFIG.bin files in the previous step was taken from your previous dashboard updflash.bin, or was taken from a dump you took off your currently working JTAG, then use the same steps above but check the box labelled SMC. You'll find an SMC.bin in the same place you found KV/SMC_CONFIG.bin.
If you're using your original nand (not recommended unless you know your wiring schema), then you will need to pick an SMC for the JTAG wiring in use. You can find SMC files for the AUD_CLAMP method of wiring (the preferred choice) in this file. Remember: Using the wrong SMC file can b0rk your JTAG, to play it super safe, take a dump of your nand using Flash360, and extract the SMC from that using 360 Flash Tool
Copy smc.bin to C:\fbBuild\mydata
Build freeBOOT
Open a command prompt, go to C:\fbBuild and type the followingfbbuild -c <model> -d mydata -f <dashboard> updflash.bin
<model> is either xenon, falcon, zephyr, jaspersb, jasper256, jasper512
<dashboard> is the name of the folder holding the dashboard files (e.g. 13604)
fbBuild will build freeBOOT as updflash.bin - copy it to USB, boot to Xellous and flash it.
Post-Install
Download the full system update - www.xbox.com/en-GB/system-update-usb
Check the version number in the filename matches your newly installed dashbaord version.
Extract to a USB stick (blank)
Insert USB stick into console
Power console on, accept the update, the console will apply and then reboot.
Links
Previous post detailing (with pictures) the steps above, with minor differences because that was dashboard 12625
[url=https://us.v-cdn.net/6034073/uploads/attachments/6737/151641.zip[/url]0 -
Lost your original nand or keyvault & smc_config.bin?
I recently found myself in this predicament with one of my own JTAGs. I made a balls of it when I thought it'd be a good idea to JTAG with a few beers. Simply put I have no idea if I took a nand dump of the console, but if I did it was deleted. Then I built freeBOOT using a KV/Config from a different Jasper. That left me in the situation where I had no original nand backup (not a big deal) but more importantly, no keyvault and no smc_config.bin.
Side effects
The JTAG worked fine, but the DVD drive refused to read any DVD. Xellous reported the CPU key, but had a "kv_read_error". The console MAC address (for ethernet) is stored in SMC_Config, which means I now had two consoles on my network with the same MAC address - not a good thing either.
More details
The Keyvault is encrypted with a CPU key. So you might think that the solution would be to get a keyvault, decrypt it with the CPU key from the console the keyvault came from, and re-encrypt it with the CPU key from the broken console. Nice idea in theory, but in practice it didn't work. Re-encrypting the keyvault seemed to change the hash of the KV, producing a rainbow-lights issue (flashing RROD where two lights are red, two green, and they alternate in sequence).
In fact, any modification to the Keyvault, because it's a KV Type 2, resulted in either no video output at all or a Christmas Lights scenario. I tried building a freeBOOT with the keyvault hash-check disabled but that never worked (though it should
)
Solution
The solution is to flash the console with a KV/SMC_Config and then flash the DVD drive with the key/OSIG from that Keyvault. So you build an updflash using the KV/SMC_Config from a donor console using that donor console CPU key.
Xellous will always report a kv_read_error on this console because Xellous uses the CPU key from the hardware, and uses that key to try decrypt the keyvault which clearly won't work. However, the DVD key/OSIG matches the key in the keyvault so the console will play games.
Of course you might still have the issue with the MAC address, but you can hexedit smc_config.bin to change that 0 -
-
-
For feck sake TV, I'm on 13599 all of an hour. Could you not have wrote this earlier?
Will Dashlaunch work on Freeboot 13604 yet?
Ah well, it's prob the most fun I get outta 360's tbh so bring it on again :rolleyes::D
Hah, 13604 is out a few days now :P Dashlaunch v2.25 was released for Dash 13604Regards your kv issue above, essentially your solution involves cloning the identity of a donor console? Disregarding mac etc, but purely from a security crednetials point of view?
Nice solution, where there any strange effects on your lan with two identical mac addresses? I presume not because it wan't online, but ftp'ing etc might be glitchy/broken?
Yup, cloned not only the KV, but the config as well. Dodgy enough given that the LDV values for CF might not match, which is why it was important I got a KV/Config from a similar model. It's not an ideal solution, but neither was losing the fecking kv/smc_config in the first place and at least I have a DVD drive to use.
I didn't notice any strange effects but that's because the JTAG downstairs has no network. I can imagine problems, especially with DHCP because that's how machines identify who has what IP address (Mac addresses) and the router keeps track of that. Best bet is to not lose the smc_config.bin, but hexediting the MAC to change it is possible too - there may even be an SMC Config tool for the job, I never bothered researching - I just chose another KV/Config from another jasper that isn't in the house
0 -
Advertisement
-
hi lads have a xbox360 im looking to get jtagged with the new hack(reset glitch and chip), any of you guys provide the service?
I've a xbox 360 elite model with a 20gb HD and hdmi connection on the back.
Im based in Carlow but could possibly drive or deliver the console to you 0 -
torrestorres wrote: »hi lads have a xbox360 im looking to get jtagged with the new hack(reset glitch and chip), any of you guys provide the service?
I've a xbox 360 elite model with a 20gb HD and hdmi connection on the back.
Im based in Carlow but could possibly drive or deliver the console to you
Anyone offering a service advertises here - http://www.boards.ie/vbulletin/showthread.php?t=2055478489
Pay special attention to the first post, no service requesting.
0 -
Anyone offering a service advertises here - http://www.boards.ie/vbulletin/showthread.php?t=2055478489
Pay special attention to the first post, no service requesting.
oops sorry 0 -
-
-
-
-
-
-
Advertisement
-
-
davidsatelle100 wrote: »deleting it worked.
Helix i had tried all types of systemupdate variations. Dashlaunch is why you have to rename it to $$ as it blocks the normal folder
Glad you got it sorted, I had the same issue myself with the 13604 update not taking after a flash, only deleting the old System/Avatar data worked too 0 -
TouchingVirus wrote: »Glad you got it sorted, I had the same issue myself with the 13604 update not taking after a flash, only deleting the old System/Avatar data worked too
saves me running over to you panicking;)0 -
-
-
TouchingVirus wrote: »Never used it, no harm in trying and letting us know how you get on
Haha, no harm at all to you my friend Harm to me if it fecks up like coolshrimps sh1te 0 -
Advertisement
-
Ok, two options using xeBuild, manual command line method, & an additional gui frontend for it:
Errors using the command line method:
You can see there are two errors, one regards the cfldv not being set, & the other regards the dvd region.
I've no idea what the cfldv is, & I'd rather not flash the image without knowing what that is. The dvd error wouldn't bother me, strange though that fbbuild doesn't pick up on that.
Using the gui frontend:
You can see here that it's only the same dvd error I'm getting. The cfldv is set to 2 here, as opposed to defaulting to 1 by the commandline tool. So I can only assume its an option/flag I'm checking in the gui tool. Also the gui tool uses an existing image for some source files, so perhaps its gathered from that?
I'm a little distrustful of gui wrappers, so any help would be appreciated0 -
Ok all sorted I think. Using 360Flash tool, you can find out the cfldv value of an existing nand dump, it's the highest number so:
Tells me my cfldv version is 2, so the gui tool obviously determined that by analysing the pre-existing nand dump I supplied it.
In the options.ini file in the 'mydata' folder of xebuild, you simply fill in the value. I also set the dvd region as 2 to eliminate the other error.
End result?
I'll flash it tomorrow & report the results.0 -
-
-
-
Advertisement
-
-
All sorted, ran the 14699 Avatar Update, installed Dashlaunch 2.7 & used my existing launch.ini, & FSD downloaded & installed 2.2 itself. So thats the Falcon up as current as current.
Thoughts on the process? Very miniscule change using xeBuild, just use the -? command to see the example switches etc. Otherwise its business as usual. I might document the Jasper process & throw it up here to keep the thread alive for us peasant jtag users. RGH users be damned (joking aside though xeBuild will generate Glitch images also, so its relevant for both hack types) 0 -
TouchingVirus wrote: »Build Instructions (Updated for latest xeBuild v1):
For simplicity you need the following:
1) Your CPU Key
2) A copy of your nand (original or FreeBOOT) and SMC
3) Dashboard Data (Google for "xxxxx Dashboard data" where XXXXX is the version number e.g. 12611, 13599, 14699
4) xeBuild (xbins -> /XBOX 360/development/xeBuild/)
Getting ready
Download xeBuild and extract it to a folder - say C:\xeBuild
Open your dashboard data zip file and extract the contents to C:\xeBuild\<version_number> e.g. for 14699.zip, extract the contents to C:\xeBuild\14699. The folder should already exist in C:\xeBuild anyway.
Edit C:\xeBuild\1blkey.txt. On the first line is a dummy key - replace it with DD88AD0C9ED669E7B56794FB68563EFA
Edit C:\xeBuild\mydata\cpukey.txt. On the first line is a dummy key - replace it with the CPU key of the console.
Extracting KV and SMC_CONFIG.bin
Open up 360 Flash Tool v0.97 and click Settings->Options. Tick the box that says "Extract ibuild compatible files". Then open your nand 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 into it, then into data and you will find two files - kv.bin and smc_config.bin. Copy these two files to C:\xeBuild\mydata.
Picking the right SMC (not for Xenon consoles)
This step is very important if your console is not a xenon - flashing the wrong SMC can end your JTAG If the nand file you used to extract the KV.bin and SMC_CONFIG.bin files in the previous step was taken from your previous dashboard updflash.bin, or was taken from a dump you took off your currently working JTAG, then use the same steps above but check the box labelled SMC. You'll find an SMC.bin in the same place you found KV/SMC_CONFIG.bin.
If you're using your original nand (not recommended unless you know your wiring scheme), then you will need to pick an SMC for the JTAG wiring in use. You can find SMC files for the AUD_CLAMP method of wiring (the preferred choice) in this file. Remember: Using the wrong SMC file can b0rk your JTAG, to play it super safe, take a dump of your nand using Flash360, and extract the SMC from that using 360 Flash Tool
Copy smc.bin to C:\xeBuild\mydata
Setup xebuild
Place an existing nand dump into the 'mydata' folder of xeBuild. This will allow xeBuild to determine various system variables. You need to rename the dump file to 'nanddump.bin' without the quotes.
Build freeBOOT
Open a command prompt, go to C:\xeBuild and type the followingxebuild -t <image type> -c <model> -d mydata -f <dashboard> updflash.bin
<image> is either glitch, jtag or retail
<model> is either xenon, falcon, zephyr, jaspersb, jasper256, jasper512 etc etc
<mydata> is where your per-console files are, cpukey.txt etc
<dashboard> is the name of the folder holding the dashboard files (e.g. 14699)
xeBuild will build freeBOOT as updflash.bin - copy it to USB, boot to Xellous and flash it.
Post-Install
Download the full system update - www.xbox.com/en-GB/system-update-usb
Check the version number in the filename matches your newly installed dashbaord version.
Extract to a USB stick (blank)
Insert USB stick into console
Power console on, accept the update, the console will apply and then reboot.
Links
Previous post detailing (with pictures) the steps above, with minor differences because that was dashboard 12625
Patched SMC files (AUD_CLAMP Wiring) for non-Xenon consoles
QUOTED & UPDATED FOR A 14699 BUILD USING XEBUILD, thanks TV0 -
-
-
-
-
-
-
-
Advertisement
Advertisement