Print

[STICKY_BUD]

QUOTE(tk_saturn @ Feb 21 2011, 05:43 PM)

Skip both. Not doing so may cause tissues.

ok, so skip that step eventhough i do have a 256mb jasper arcade? if it works, i am definitely sending another pm to looouky. i already sent one about the 2 step 8e's.

thanks again. i think i am straight on your suggestions now.

[STICKY_BUD]

still green light and no screen with ANY updflash.bin i can make for my 256mb jasper arcade console. i am using a standard av cable. i can still boot xellous and i have tried making freeboot in EVERY combination...
1. using step 8d and skipping 8e
2. skipping both step 8d and 8e
3. skipping 8e and using 8e
4. using both step 8d and 8e

i have reflashed free60.bin all 4 times in order to get back into xellous because eject does not do it after the update.

at this moment, i am very unsure what to do next besides trying to restore my fullnand2.bin and cross my fingers that it still boots.

anybody have some advice for me?

[niabi]

QUOTE(STICKY_BUD @ Feb 22 2011, 12:58 AM)

still green light and no screen with ANY updflash.bin i can make for my 256mb jasper arcade console. i am using a standard av cable. i can still boot xellous and i have tried making freeboot in EVERY combination...
1. using step 8d and skipping 8e
2. skipping both step 8d and 8e
3. skipping 8e and using 8e
4. using both step 8d and 8e

i have reflashed free60.bin all 4 times in order to get back into xellous because eject does not do it after the update.

at this moment, i am very unsure what to do next besides trying to restore my fullnand2.bin and cross my fingers that it still boots.

anybody have some advice for me?

just one thing that drove me crazy for a while... maybe it will be the same for you, but make sure the xbox is not connected tru HDMI xellous does not work by HDMI (or mine at least doesn't) and it just shows a green light no display... just something to check as I don't have a jasper to help on the flashing

[STICKY_BUD]

instead of reflashing my fullnand and giving up, i started doing some other things and ended up with 0022 before i finally went to sleep. yeah so i realized that i was definitely doing something very wrong over the last several days and i decided to start over. i deleted all of the scene releases and downloaded everything over again to a new folder structure. i figured a fresh start was in order...

i only made a little progress though and still need some help.

now, i am back to using mana100 xellous; i have not tried anything else today. my console is verified as an exploitable jasper 256 arcade. i am trying my best to do every step as instructed, but still not getting nxe to boot.

one thing that is definitely different with the freshly downloaded files is that i can push eject now and boot back into xellous after the E72 error; instead of green light/blank screen. that is progress!

since i am using freeboot .04, one of the things i decided to do was download patches_jasper.bin from the dash_launch_v2.08_for_12611 release (instead of the file for 9199 linked in the tut)...

at this point, i have tried creating freeboot by:
-using step 8d (with the renamed smc.bin file from the mana100 release) and then skipping step 8e
-using step 8d (as above) and then using 8e with the 12611 patches
-skipping steps 8d and 8e

edit: i also tried easy freeboot on my windows 7 pc just because it was a quick option to attempt and still received the E72 error.

my head is spinning from all of the various threads i have searched through today. any advice from anyone is appreciated!

This post has been edited by STICKY_BUD: Yesterday, 03:50 AM

[DuckOfDeath]

I'm on step 8, and having a hard time getting freeBOOT Toolbox 0.04 Maker v2.7a to create an updflash.bin file for me.  It gets to 38% and gives a critical error: "your dump has not been properly extracted. The reason is unknown."  

I have followed your tutorial with one exception: I started using Grim's first step, ie, I read 3mb of the nand over the LPT, like this:  nandpro lpt: -r3 c1.bin

So, in step 7d, I made a 2mb copy of my c1 by: nandpro: c1.bin: -r2 2mb.bin.  

I then used this: nandpro fullnand1.bin: -w16 2mb.bin 0 to create the complete full nand file.

I get the freeboot toolbox error if I use the 2mb or 3mb c1.bin file.  

One thing of note, is in step 7c, two of my 5 full nand dumps did not match.  I used one of the three that did match for step 7d.  Is this normal?

Any suggestions?

-Duck!

[Looouky]

That issue is usually related to windows 7, if you ran the program in windows xp perhaps you wouldn't get the error.

[DuckOfDeath]

I now have a freeBOOT.bin file generated under xp.  My nand dumps from XeLLous actually all matched there too--odd.  However, when I put the file, renamed to updflash.bin on the console, XeLLous says it flashes, but after a power cycle it still powers on to XeLLous.  

I dumped the nand again and it does not match the updflash.bin that was supposed to have been flashed.  It doesn't match the old nand dump either.  

-Duck!

[AZImmortal]

QUOTE(DuckOfDeath @ Feb 23 2011, 08:56 PM)

I now have a freeBOOT.bin file generated under xp.  My nand dumps from XeLLous actually all matched there too--odd.  However, when I put the file, renamed to updflash.bin on the console, XeLLous says it flashes, but after a power cycle it still powers on to XeLLous.  

I dumped the nand again and it does not match the updflash.bin that was supposed to have been flashed.  It doesn't match the old nand dump either.  

-Duck!

Besides what mickcris has already mentioned about connecting your DVD drive, I wanted to add that your dumped NAND will never match what you flashed with after you turn on your console.  In order to see if everything was written correctly, you would need to dump the NAND before turning on your console.

[DuckOfDeath]

QUOTE(mickcris @ Feb 23 2011, 11:28 PM)

Do you have the DVD drive connected?  If it is disconnected it will give a tray open signal and boot to xellous with freeboot 0.04.  I made this mistake before.

That was it!  It's booting LIKE A BOSS now!  I had borked my DVD drive removing an old dualboot sst mod I had installed years ago.  It's up and running with a donor drive spoofed as my original.  Jungleflasher is sooo much better than back when I last flashed a drive with the first extreme fw.  Five minutes and I had a flashed and spoofed drive. w00t!

QUOTE(AZImmortal @ Feb 24 2011, 01:58 AM)

Besides what mickcris has already mentioned about connecting your DVD drive, I wanted to add that your dumped NAND will never match what you flashed with after you turn on your console.  In order to see if everything was written correctly, you would need to dump the NAND before turning on your console.

That's good to know.  I'd ask what the 360 does to it after a boot, but honestly, I don't care-- My box boots, the jtag works!  

Thanks to everyone who helped me.  I know my way around a first gen xbox blindfolded, but I never really got into the 360--it's all new to me.  But now I've got homebrew!  Yay!

-Duck!

[tk_saturn]

CODE

nandpro fullnand1.bin: -r256 configx.bin ef7 16  
nandpro updflash.bin: -w256 configx.bin ef7 16

 

and then open the updflash.bin and see if the resulting file has your own readable config.

[tk_saturn]

CODE

nandpro fullnand1.bin: -r256 configx.bin ef8 8  
nandpro updflash.bin: -w256 configx.bin ef8 8

as the config is in block 1DF on a 256MB.

Thanks for the bump too...

[STICKY_BUD]

QUOTE(tk_saturn @ Feb 25 2011, 08:15 PM)

Sorry, that was a mistake. Looks like it should be

CODE

nandpro fullnand1.bin: -r256 configx.bin ef8 8  
nandpro updflash.bin: -w256 configx.bin ef8 8

as the config is in block 1DF on a 256MB.

Thanks for the bump too...

thanks again tk_saturn, you deserve thanks for the help you offfer others in this forum and i know everyone likes receiving a bst bump.

back on topic: i have not actually started loading the console with apps yet, but i will keep this in mind. at the moment, i am pretty sure looouky handled this issue for me because the wiped config.bin data was the first thing he noticed about the files i sent him.

i am not sure if he was able to recreate the data from scratch or if he was able to get the config.bin data from a different set of files i emailed him later, but he was aware of that issue while he was helping me to create a new set of files to flash and archive.

[mat7699]

For those having problem with kv.bin and get stuck at 38% in freeBOOT tool box , try replacing bad block of your original nand in their normal place. Then flash with xbrflash for linux, it will remap block for you!

I had this problem, specialy i had block 1 bad, and it contain the kv!

I used jtag tool 1.70 to replace bad block then i confirmed in flash360 with the key that it was good, then i went on with freeboot tool box !

I spent so much time on that, i had to share !

[death69inc]

ok i love you lmfao   1st aud clamp that worked 2nd attempt

zephyr  reg jtag resistors  1 in 10 would boot other e74 worst I have ever seen

then aud clamp boxxdr method had xellous working no boot green center only so fig wiring ok

add your tut and I get a zephyr that has booted 10 out of 11 times  

now if I can get my jasper to even act like it is jtagged at all no xell


THANKS FOR TUT

Ok well not booting as well as stated now but still much better than before damn zephyr's

 

[death69inc]

back to e79 everytime )*@%&)*@%&)@%&@