Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About GoRo2010

  • Rank
    RMS Freshman
  1. Ah, now that makes sense I am a total NOOB when it come to these things, but I try to read up a lot before asking dumb questions, I assumed that all command lines was set for all models. Is this normal thou? "ERROR: Unable to decrypt KV using specified CPUKey!" - I can open the KV in J-runner thou. Another question, can you jump dash versions so lets say I don't do this update but do the next one released (As this one is only related to Live), will that have any impact or do you need to update every version? - "I know this is total NOOB question" - My commonsense says that it will not be a problem, just want to confirm Thank You
  2. Great, thank you for the clarity. I just thought I would share my findings I will rebuilt the image again in the right command sequence. Any reason why this was removed with the new xeBuild version?
  3. Good Day Swizzy, 1st off I want to start to say thank you to you and your team for supporting a huge community in need I have a quick question thou, I see the comment that you made here: As this is my 1st time trying to update my dash version (Hopefully not bricking it) , I have not seen this command in any guides that I have read, I have also gotten the same error message like the OP, but with this command it is not happening anymore, I have read your guide in detail (unless if I am blind) I don't see this part in your guide, maybe worthwhile to update if it is not there This is the link I used to read your guide: http://forum.homebrew-connection.org/index.php?topic=144.0 Can you also please advise, my NAND was dumped and patched the 1st time via J-Runner, would it matter if I update it now via exBuild? This is my log after the command line addition, I have not written the NAND as yet to test, as I really don't want to brick it My Log: ================================== Swizzy's xeBuild GUI version 2.098 Log Started: Monday 2016/10/03 11:32:45 AM ================================== *** Some console information *** CB Version: 0 ERROR: Unable to decrypt KV using specified CPUKey! This means the log will NOT contain information from your keyvault, it can be caused by etheir badkey or badblock/corrupt keyvault Using xell-reloaded for Glitch hack Including dashlaunch... Done! Including custom dashlaunch settings (launch.ini)... Done! Copying nand to data directory, this may take a while... Done! Checking if SMC is Glitch or Retail... Dumping current SMC... Done! Checking SMC... SMC is Glitch patched! it will be used the way it is... Disabling FCRT.bin check... Parameters sent to xeBuild: -noenter -t glitch2 -c corona4g -d data -f 17502 -b ... -p ... -a nofcrt output.bin -o patchsmc Building nand using xeBuild (this may take a while): --------------------------------------------------------------- xeBuild v1.17.785 --------------------------------------------------------------- base path changed to C:\Users\....\Downloads\xeBuild_GUI_2.098\files ---- { Image Build Mode } ---- building glitch2 image done! fsroot found ok! --------------------------------------------------------------- output.bin image built, info: --------------------------------------------------------------- Kernel : 2.0.17502.0 Console : Corona NAND size : 48MiB MMC (system only) Build : Glitch (v2) Xell : power on console with console eject button Serial : ConsoleId : MoboSerial: Mfg Date : 07/03/2014 CPU Key : 1BL Key : DVD Key : CF LDV : 4 KV type : type2 (hashed - unchecked, master key not available) --------------------------------------------------------------- xeBuild Finished. Have a nice day. --------------------------------------------------------------- Thank You! ** UPDATE: I see on your printscreen, the command is by default there, as of the new version v2.089, it have been excluded and your guide only shows the 4g part highlighted **This is the current default setting now "-noenter -t glitch2 -c corona -d data -f 17502 -b D................................................A -p 1.......................................F9 -a nofcrt output.bin"
  • Create New...