You are viewing our Forum Archives. To view or take place in current topics click here.
What the hell is this lol?
Posted:
What the hell is this lol?Posted:
Status: Offline
Joined: Jul 04, 201211Year Member
Posts: 343
Reputation Power: 15
Status: Offline
Joined: Jul 04, 201211Year Member
Posts: 343
Reputation Power: 15
Hello, TheTechGame, i've put the disk in my computer what came with my Falcon jtag called "Falcon Jtag Files" and brought this up "Screenshot below", you can't see the information i've blocked out, because thats private.
Screenshot
Thanks and am i, on the least dash that can be done? (if you get me)
Screenshot
Thanks and am i, on the least dash that can be done? (if you get me)
#2. Posted:
Status: Offline
Joined: Nov 18, 201112Year Member
Posts: 1,184
Reputation Power: 51
That's a notepad file
- 0useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Jul 04, 201211Year Member
Posts: 343
Reputation Power: 15
Status: Offline
Joined: Jul 04, 201211Year Member
Posts: 343
Reputation Power: 15
Mobs wrote That's a notepad file
I meant the information & Files :facepalm:
- 0useful
- 0not useful
#4. Posted:
Status: Offline
Joined: Dec 16, 201013Year Member
Posts: 1,957
Reputation Power: 98
Status: Offline
Joined: Dec 16, 201013Year Member
Posts: 1,957
Reputation Power: 98
The notepad just says the information about your console, like the motherboard type, keyvault type, when it was manufactured, and region.
For region specifics:
[ Register or Signin to view external links. ]
cpukey is a text file that most likely has your cpu key. (needed when updating dashboard)
falcon_hack_aud_clamp.bin is probably your nand from when it was being jtaged. (it has the aud clamp hack, also important when updating dashboards)
KV_Info is a text file that most likely has your keyvault information. (this is useless unless you can go online)
nandflash14719.bin is probably a modded version of your original nand, but it is on dashboard 14719.
original.bin is most likely your original nand.
xenon.elf is used to flash a nand file through xellous.
Hope that helped.
For region specifics:
[ Register or Signin to view external links. ]
cpukey is a text file that most likely has your cpu key. (needed when updating dashboard)
falcon_hack_aud_clamp.bin is probably your nand from when it was being jtaged. (it has the aud clamp hack, also important when updating dashboards)
KV_Info is a text file that most likely has your keyvault information. (this is useless unless you can go online)
nandflash14719.bin is probably a modded version of your original nand, but it is on dashboard 14719.
original.bin is most likely your original nand.
xenon.elf is used to flash a nand file through xellous.
Hope that helped.
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Jul 04, 201211Year Member
Posts: 343
Reputation Power: 15
Status: Offline
Joined: Jul 04, 201211Year Member
Posts: 343
Reputation Power: 15
marsupiallizard wrote The notepad just says the information about your console, like the motherboard type, keyvault type, when it was manufactured, and region.
For region specifics:
[ Register or Signin to view external links. ]
cpukey is a text file that most likely has your cpu key. (needed when updating dashboard)
falcon_hack_aud_clamp.bin is probably your nand from when it was being jtaged. (it has the aud clamp hack, also important when updating dashboards)
KV_Info is a text file that most likely has your keyvault information. (this is useless unless you can go online)
nandflash14719.bin is probably a modded version of your original nand, but it is on dashboard 14719.
original.bin is most likely your original nand.
xenon.elf is used to flash a nand file through xellous.
Hope that helped.
OMG this is so helpful, what is the least dash a Jtag can update too and how do i do it?
+rep for you, when answered
Thank you very much.
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Dec 16, 201013Year Member
Posts: 1,957
Reputation Power: 98
Status: Offline
Joined: Dec 16, 201013Year Member
Posts: 1,957
Reputation Power: 98
[ Register or Signin to view external links. ]
Basically he is dumping (backing up) his current nand using Flash360, then putting that nand (flashdmp.bin) on a different USB so he can put it on his computer.
At computer: Run the Xebuild GUI.
-Open the flashdmp.bin file
-Make sure you have the correct motherboard and build type selected
-Put your CPU key in
-Select the kernal number (15574)
-Click generate image
Once that is done, you should have a file named updflash.bin, just flash this to your console through Flash360.
Basically he is dumping (backing up) his current nand using Flash360, then putting that nand (flashdmp.bin) on a different USB so he can put it on his computer.
At computer: Run the Xebuild GUI.
-Open the flashdmp.bin file
-Make sure you have the correct motherboard and build type selected
-Put your CPU key in
-Select the kernal number (15574)
-Click generate image
Once that is done, you should have a file named updflash.bin, just flash this to your console through Flash360.
- 0useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.