Post by: Mack702 on October 25, 2011, 07:33:00 AM
Post by: razkar on October 25, 2011, 02:00:00 PM
QUOTE(playonlcd @ Oct 25 2011, 04:12 PM) 
I also expect a tool from best big, as in the usual manner.
It will come soon
Post by: Nothinbeter2do on October 25, 2011, 02:01:00 PM
So we still need to manually extract smc.bin? What's the point? Even when I manually put smc.bin in the my360 folder, I still have to put kv.bin and smc_config.bin in there too.
Also, when it fails, it still says that it created the image successfully.
Post by: Rogero on October 25, 2011, 02:18:00 PM
QUOTE(Nothinbeter2do @ Oct 25 2011, 10:01 PM)
http://i.imgur.com/5Hg2Z.png
So we still need to manually extract smc.bin? What's the point? Even when I manually put smc.bin in the my360 folder, I still have to put kv.bin and smc_config.bin in there too.
only 2 files are needed : nanddump.bin and cpukey.txt in "Data\my360" folder, u got this error because the nand image was not found in the correct path.
Also smc.bin, kv.bin, fcrt.bin/fcrt.bin.meta and CF LDV are all automatically extracted and u don't need to provide any of them.
Cheers
Post by: Rogero on October 25, 2011, 03:11:00 PM
------------------------------------------------------------------------------------------------------
- Updated BestPig's "fcrt_extractor" to version 0.3
- Eliminated one step from the Trinity image creation for simpler operation
This is the Final Version, no more updates are necessary.
Credits to ggbuild/fbbuild/freeboot and 360FlashTool teams and devs.
Credits and big thanks to BestPig for sharing his awesome fcrt_extractor.exe program.
Cheers
Post by: Nothinbeter2do on October 25, 2011, 04:52:00 PM
QUOTE(Rogero @ Oct 25 2011, 04:18 PM)
only 2 files are needed : nanddump.bin and cpukey.txt in "Data\my360" folder, u got this error because the nand image was not found in the correct path.
Also smc.bin, kv.bin, fcrt.bin/fcrt.bin.meta and CF LDV are all automatically extracted and u don't need to provide any of them.
Cheers
Using a different NAND file, it worked just fine. I guess the first NAND dump wasn't working because it had bad blocks.
Post by: darklord88 on October 25, 2011, 05:21:00 PM
i love xbox scene
Post by: wlintek on October 25, 2011, 05:53:00 PM
but i have a problem. on my falcon, i had an hacked image and everthing worked just fine.
i used this tutorial:
then i tried easy ggBuild to create another image and flashed to the same falcon, after that i found it boots very erastic. some times it just does not boot at all.
i compared two nands that i careated using different methods, it shows 62 non-matched blocks.
i finally flashed my first image back , everything works fine again.
Post by: steveo1978 on October 25, 2011, 07:44:00 PM
Rogero your link was removed because it contains copyrighted material.
Post by: xandura on October 25, 2011, 11:30:00 PM
Post by: Rogero on October 26, 2011, 01:31:00 AM
QUOTE(wlintek @ Oct 26 2011, 01:53 AM)
i compared two nands that i careated using different methods, it shows 62 non-matched blocks.
The program itself uses ggbuild v0.33b to create the image, it doesn't modify the image in any way, it just make it easy to choose the correct parameters for each console type.
Also you can never have 2 matching glitch images built from the same nand image, even if you used ggBuild v0.33b manually (you can simply try it) and that's because of the hashing algorithms used in the build process
QUOTE
i tried easy ggBuild to create another image and flashed to the same falcon, after that i found it boots very erastic. some times it just does not boot at all.
That's very normal, my same Jasper sometimes boots directly in 1 second after power up, sometimes takes more then a minute to boot with the very same image flashed. That's the nature of the glitch hack itself, usually a cold CPU will glitch better then it does when it's warm.
QUOTE(steveo1978 @ Oct 26 2011, 03:44 AM)
Rogero your link was removed because it contains copyrighted material.
Sorry about the link, it wasn't intentional, just forgot to remove it after i pasted my post
Post by: moreniu on October 26, 2011, 12:29:00 PM
I have a question, I am using bestpigs tool to generate the ecc file I flashed to my jaspe 256 nand to recover it's dvdkey, it worked just fine, now I am trying to have it running the ggbuild on it, but what do I do with the updflash file? Put it on an usb drive or simple flash it directly to the nand?
Sorry for the noobish, and thanks again!
Post by: SNAAAKE on October 26, 2011, 02:48:00 PM
flashing with the cable is fine too but for future updates Id obviously prever doing it from xell with a flash drive.
Post by: boflc on October 26, 2011, 05:12:00 PM
QUOTE(moreniu @ Oct 26 2011, 01:29 PM)
.. but what do I do with the updflash file? Put it on an usb drive or simple flash it directly to the nand?
QUOTE(SNAAAKE @ Oct 26 2011, 03:48 PM)
^ I am wondering about this question too.
- source rawflash_v3 (thanks [cOz]!).
- place rawflash's xenon.elf in the root of a fat32 flash drive.
- rename the output of ggbuild or rogero's tool to nandflash.bin and place it in the root of the same fat32 flash drive
- plug the fat32 flash drive into your glitched system && power it on via eject
- profit
Post by: Rogero on October 27, 2011, 03:37:00 AM
QUOTE(playonlcd @ Oct 27 2011, 02:14 AM)
I am having the same error as Nothinbeter2do, even if i have copied the nanddump.bin in my360 data folder and placed cpukey in cpukey.txt.
I am trying to make the image for a Jasper 512MB, with just first 64 blocks. I should have the whole image 512MB or 64 is enough?
I kow that it enough 64, but just to make sure ...
http://i.imgur.com/5Hg2Z.png
This error means ggBuild couldn't find your nand image, please make sure you have the file name right "nanddump.bin" placed in "Data\my360".
Also for Jasper256/512 you only need a 66MB nand file, I just tried 3 different Jasper512 dumps, and all images was created in less then 2 seconds each.
Cheers
Post by: playonlcd on October 27, 2011, 07:52:00 AM
QUOTE(Rogero @ Oct 27 2011, 12:37 PM)
This error means ggBuild couldn't find your nand image, please make sure you have the file name right "nanddump.bin" placed in "Data\my360".
Also for Jasper256/512 you only need a 66MB nand file, I just tried 3 different Jasper512 dumps, and all images was created in less then 2 seconds each.
Cheers
Thanks for answering.
The fact is that it is for sure named "nanddump.bin", as i just copied the name.
I'll try again tonight.
Post by: playonlcd on October 27, 2011, 03:38:00 PM
QUOTE
ggBuild v0.33.273
---------------------------------------------------------------
**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
**** could not read kv.bin (-1) ****
******* ERROR: critical bootloader files are missing, cannot proceed!
***** FATAL BUILD ERROR: -1 unable to complete NAND image
---------------------------------------------------------------
ggBuild Finished. Have a nice day.
---------------------------------------------------------------
press <enter> to quit...
---------------------------------------------------------------
**************** WARNING *************************
nanddump.bin has NAND memory unit data, make
sure you back up any important data off the
internal MU before flashing a new image!
****************************************************
**** could not read kv.bin (-1) ****
******* ERROR: critical bootloader files are missing, cannot proceed!
***** FATAL BUILD ERROR: -1 unable to complete NAND image
---------------------------------------------------------------
ggBuild Finished. Have a nice day.
---------------------------------------------------------------
press <enter> to quit...
LE:
Jesus, i am using to much Linux.
Also i was renaming the cpykey.txt with extension txt, but windows got it by default.
So, people, pay attention, rename only with "nanddump" and "cpukey", and it is good to go.
Thaaaaanks!
Now lets party!
Post by: wlintek on October 28, 2011, 01:01:00 AM
QUOTE(Rogero @ Oct 27 2011, 10:37 AM)
Also for Jasper256/512 you only need a 66MB nand file, I just tried 3 different Jasper512 dumps, and all images was created in less then 2 seconds each.
Sorry, just to make sure , 64Mb or 66MB of the nand for Jasper 512?
Post by: Rogero on October 28, 2011, 02:20:00 AM
QUOTE(wlintek @ Oct 28 2011, 09:01 AM)
Sorry, just to make sure , 64Mb or 66MB of the nand for Jasper 512?
It is a convention to say the first "64MB" from the nand is the Flash and the rest is for the MU
but actually when you dump it using -r64 with nandpro the nand dump is 66MB in size.
The original nand dump and the glitch-hack image for a Jasper256/512 must both be:
66 MB = 67584 KB = 69,206,016 bytes
Post by: wlintek on October 28, 2011, 07:44:00 AM
now, do i just use nandpro usb: -w64 updflash.bin to flash the nand?
Post by: Rogero on October 28, 2011, 09:04:00 AM
QUOTE(wlintek @ Oct 28 2011, 03:44 PM)
thanks Rogero, i dumped first 64mb and created image using your app. when finished i have 66mb updflash.bin
now, do i just use nandpro usb: -w64 updflash.bin to flash the nand?
yes, -w64 will do it fine
Post by: domina on October 29, 2011, 01:05:00 PM
Is there anyone with the same problem? Any suggestions?
Post by: Rogero on October 30, 2011, 10:44:00 PM
--------------------------------------------------------------------
- Updated "Easy ggBuilder" to "360 Multi Builder" with ECC/Jtag/Glitch & Retail image creation.
- Added Auto-Build ECC Glitch image "image_00000000.ecc" when "cpukey.txt" is missing.
- Added startup checks for "nanddump.bin" and "cpukey.txt" files existence.
- Jtag/Freeboot 13604 image creation with built-in Dashlaunch v2.25 patches & Xell-Reloaded.
- Glitch Hack 13604 image creation with built-in Dashlaunch v2.25 patches & Xell-Reloaded.
Credits to ggbuild/fbbuild/freeboot/360FlashTool & Dashlaunch teams and devs.
Credits and big thanks to BestPig for sharing his awesome fcrt_extractor.exe program.
official site: www.tortuga-cove.com
Post by: steveo1978 on October 30, 2011, 11:47:00 PM
Post by: guerriero di pace on October 31, 2011, 11:30:00 AM
with your tool is also possible to rebuild an original nand from a modified nand?
thanks
Post by: steveo1978 on October 31, 2011, 12:24:00 PM
QUOTE(guerriero di pace @ Oct 31 2011, 12:30 PM)
with your tool is also possible to rebuild an original nand from a modified nand?
There seems to be an option for that in there. So yeah you should be able to.
Post by: dahummer on November 01, 2011, 07:29:00 PM
QUOTE(lenselijertje @ Nov 1 2011, 01:20 AM)
Worked perfect for creating a xell image and ggbuild image, thank you!
same here got my cpu key made ggbuild image flash it back now i got E71 after xbox logo any idea ?
thanks
Post by: dopper_nl on November 02, 2011, 09:58:00 AM
Got a trinity with xell booting in 10 till 20 sec. but no way it will boot a build image from one of the tools tryed all versions.
Had it running only once but never again after that the light of the 360 will be green for 30 sec and then get red with no screen on display, someone any idea what to look for (running out of idea's myself).
Post by: steveo1978 on November 03, 2011, 12:16:00 AM
Post by: Rogero on November 03, 2011, 03:34:00 AM
QUOTE(steveo1978 @ Nov 3 2011, 08:16 AM)
Thank you.
Post by: dopper_nl on November 03, 2011, 01:02:00 PM
QUOTE(dopper_nl @ Nov 2 2011, 05:58 PM)
Very nice these tools, But i still run into problems,
Got a trinity with xell booting in 10 till 20 sec. but no way it will boot a build image from one of the tools tryed all versions.
Had it running only once but never again after that the light of the 360 will be green for 30 sec and then get red with no screen on display, someone any idea what to look for (running out of idea's myself).
Problem solve use rawflash v3 to flash the rebooter to nand