You are viewing our Forum Archives. To view or take place in current topics click here.
Updating to 13604 - Bad KV?
Posted:
Updating to 13604 - Bad KV?Posted:
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Hi!
Trying to update my new JTAG (Falcon on 12611) to the latest dash [ Register or Signin to view external links. ] and I have stumbled upon a problem.
Everything is fine until I run FbBuild which is when I run into the error;
So, I ran 360 Flash Tool and get the Bad Key error;
[ Register or Signin to view external links. ]
The CPU key is set in keys, and I have also tested the CPU key and NAND of my old Xenon JTAG which works fine.
I have emailed the guy I bought it off asking for the original NAND but so far no reply.
So;
Thanks in advance for any help and ideas!
Cheers! 8)
Trying to update my new JTAG (Falcon on 12611) to the latest dash [ Register or Signin to view external links. ] and I have stumbled upon a problem.
Everything is fine until I run FbBuild which is when I run into the error;
---------------------------------------------------------------
fbBuild v0.33 (R:272)
---------------------------------------------------------------
**** could not read kv.bin (-1) ****
******* ERROR: critical bootloader files are missing, cannot proceed!
***** FATAL BUILD ERROR: -1 unable to complete NAND image
---------------------------------------------------------------
fbBuild Finished. Have a nice day.
---------------------------------------------------------------
So, I ran 360 Flash Tool and get the Bad Key error;
[ Register or Signin to view external links. ]
The CPU key is set in keys, and I have also tested the CPU key and NAND of my old Xenon JTAG which works fine.
I have emailed the guy I bought it off asking for the original NAND but so far no reply.
So;
- Is there any chance the NAND I have dumped and the original NAND would be different but the console still work fine?
- Can I buy a new Falcon CPU key and get it working that way?
Thanks in advance for any help and ideas!
Cheers! 8)
#2. Posted:
Status: Offline
Joined: Jun 19, 201112Year Member
Posts: 680
Reputation Power: 36
Status: Offline
Joined: Jun 19, 201112Year Member
Posts: 680
Reputation Power: 36
when you place a NAND into 360flashtool it shows as bad KV. Just ignore it your fine.
Please someone correct me if im wrong
Please someone correct me if im wrong
- 0useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Aug 13, 201112Year Member
Posts: 2,113
Reputation Power: 103
I had this same exact problem. Make sure you have the correct CPU key.
- 0useful
- 0not useful
#4. Posted:
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Crazed-Cracker; I continued the guide ignoring the Bad KV error the first time and once flashed the 360 displayed the Christmas tree lights error.
Zoo; I have triple checked the CPU key is correct.
Is there any reason why the CPU key in the NAND and the CPU key displayed in Xellous would be different?
Thanks again!
Zoo; I have triple checked the CPU key is correct.
Is there any reason why the CPU key in the NAND and the CPU key displayed in Xellous would be different?
Thanks again!
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Dec 11, 201013Year Member
Posts: 2,509
Reputation Power: 133
Status: Offline
Joined: Dec 11, 201013Year Member
Posts: 2,509
Reputation Power: 133
If you are going to update you need to have your cpu key.
The nand files are encrypted and the only way to decrypt them is to input the cpu key
The nand files are encrypted and the only way to decrypt them is to input the cpu key
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Nickxmodz;Yup, have the CPU key and it doesn't work with the NAND I have dumped.
My question is; If this JTAG had been banned and given a new NAND and CPU key (possible?) would the virtual fuses still display the old CPU key?
This would explain why the NAND I have dumped and the CPU key grabbed from Xellous are different.
Is there any other way to get the CPU key? From the NAND itself maybe?
Thanks!
My question is; If this JTAG had been banned and given a new NAND and CPU key (possible?) would the virtual fuses still display the old CPU key?
This would explain why the NAND I have dumped and the CPU key grabbed from Xellous are different.
Is there any other way to get the CPU key? From the NAND itself maybe?
Thanks!
- 0useful
- 0not useful
#7. Posted:
Status: Offline
Joined: Dec 11, 201013Year Member
Posts: 2,509
Reputation Power: 133
Status: Offline
Joined: Dec 11, 201013Year Member
Posts: 2,509
Reputation Power: 133
Omgyjya_Switch7 wrote Nickxmodz;Yup, have the CPU key and it doesn't work with the NAND I have dumped.
My question is; If this JTAG had been banned and given a new NAND and CPU key (possible?) would the virtual fuses still display the old CPU key?
This would explain why the NAND I have dumped and the CPU key grabbed from Xellous are different.
Is there any other way to get the CPU key? From the NAND itself maybe?
Thanks!
No unfortunetly the only way to get the cpu key is thru xell or xellous fuses 3 and 5 or fuses 4 and 6
If you write a new freeboot image of another board to this one (must be the same type of console revision)
It will change the the freeboot image and dvd key but not change the cpu key
- 0useful
- 0not useful
#8. Posted:
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
So the new image would still use the original CPU key?
I have used many different dumps from Xellous, Flash 360 and NAND flasher 360 (always with the same CPU key, of course) and always get the same result - Bad KV!
What else could have happened?
Any ideas on other things I can try?
Cheers!
I have used many different dumps from Xellous, Flash 360 and NAND flasher 360 (always with the same CPU key, of course) and always get the same result - Bad KV!
What else could have happened?
Any ideas on other things I can try?
Cheers!
- 0useful
- 0not useful
#9. Posted:
Status: Offline
Joined: Dec 11, 201013Year Member
Posts: 2,509
Reputation Power: 133
Status: Offline
Joined: Dec 11, 201013Year Member
Posts: 2,509
Reputation Power: 133
Omgyjya_Switch7 wrote So the new image would still use the original CPU key?
I have used many different dumps from Xellous, Flash 360 and NAND flasher 360 (always with the same CPU key, of course) and always get the same result - Bad KV!
What else could have happened?
Any ideas on other things I can try?
Cheers!
You need to go into the keys of 360 flash tool and add your cpu key i can team viewer you if you pm me your stuff
- 0useful
- 0not useful
#10. Posted:
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
Status: Offline
Joined: Sep 15, 201112Year Member
Posts: 27
Reputation Power: 1
As in the first post, I have even used the NAND and CPU key from my other Xenon JTAG and it works fine.
Both keys are in the database, one NAND works (Xenon) and the other doesn't (Falcon - Bad KV).
Feel free to TeamViewer though if you wish, could be good to have a second pair of eyes on it.
Thanks!
Both keys are in the database, one NAND works (Xenon) and the other doesn't (Falcon - Bad KV).
Feel free to TeamViewer though if you wish, could be good to have a second pair of eyes on it.
Thanks!
- 0useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.