Print

[ravendrow]

ok so just a note to zephyr owners if you have a problem after flashing (and unplugging in some cases) your problem might be your smc file. i recommend you dump your current xbr build with flash360 to get your  proper smc file. i was redoing my kids zephyr with the new freeBOOT 0.32 and things just weren't going right e79 rrod, which didn't make sense to me cause i had already done my xenon and my falcon and they worked great . then i remembered when i originally did there's i had to use the falcon smc in order to get i to work right. so sure enough re-built and re-flashed with falcon smc and works great now, lol and it only took 45 min to figure out.

hope this helps someone

**works same as xbr as far as booting occasional rrod or e79 turn off wait 10 sec turn it back on boots right back up

[hetster]

why do i get ibuild.exe is not a valid win32 application. i am on XP and have tried from desktop and direct from C: drive.
i have cmd window here power toy and use that. could that be the problem?

[enzo80]

Hello,

i have build freeboot 0.032 for jasper 512 succesfully, but how i can patch this image with the memory protection patch of this release ?
What i have to do with the patches-jasper.bin file in the patches-full-mem-editing folder ?

Thanks and best regards

[geoffmac]

Check in the bin folder you will see a readme and two folders 'patches [full mem editing]' and 'patches [xb1 compatibility]'

I havent done this yet but presume you take the files out of the patch folder you plan to use and drop them in 'bin' folder.

[Conundrum1911]

QUOTE(geoffmac @ Apr 19 2010, 06:35 AM)

Check in the bin folder you will see a readme and two folders 'patches [full mem editing]' and 'patches [xb1 compatibility]'

I havent done this yet but presume you take the files out of the patch folder you plan to use and drop them in 'bin' folder.

That's what I did (with the xb1 compatibility patch), and can confirm that everything seems to be working on my console post-upgrade/switch from xbr to freeboot.

[emko]

im so confused do i need to have a original dump? i have nothing someone did the flashing for me could i still make a dump with xell and use that to get this to work?

[geoffmac]

QUOTE(emko @ Apr 19 2010, 12:43 PM)

im so confused do i need to have a original dump? i have nothing someone did the flashing for me could i still make a dump with xell and use that to get this to work?

this may help handy link  

[ZprivateZ]

QUOTE(enzo80 @ Apr 19 2010, 06:23 AM)

Hello,

i have build freeboot 0.032 for jasper 512 succesfully, but how i can patch this image with the memory protection patch of this release ?
What i have to do with the patches-jasper.bin file in the patches-full-mem-editing folder ?

Thanks and best regards

Replace the patches_jasper.bin in the "bin" folder with the one from the "patches [full mem editing]" folder then remake your image.

[whackawookie]

For anyone like me who has dumped their jasper 512 with nandpro with only the flash portion and can't extract with ibuild heres a quick fix. My original dump was 68.0 MB (71,368,704 bytes) in size but the goal is 66.0 MB (69,206,016 bytes).  Make a backup of your file before going forward. Open the one you plan on using in a hex editor and make sure the ruler is extended to 2b.  
(IMG:http://i128.photobucket.com/albums/p167/whackawookie/Snap5.jpg)

now click edit and choose goto, in a hex format paste 041fffd4. Make sure everything beyond this point is null (FF).  Once you confirm, highlight from the row directly under ( so from 0420000 on)
(IMG:http://i128.photobucket.com/albums/p167/whackawookie/Snap6.jpg)

all the way to the end and hit delete.  Save the new file and confirm the new size is 66.0 MB (69,206,016 bytes)
(IMG:http://i128.photobucket.com/albums/p167/whackawookie/Snap7-1.jpg)
Throw the new file through ibuild and everything should extract fine now.

sorry for the pic sizes

[ZprivateZ]

QUOTE(whackawookie @ Apr 19 2010, 09:41 AM)

For anyone like me who has dumped their jasper 512 with nandpro with only the flash portion and can't extract with ibuild heres a quick fix. My original dump was 68.0 MB (71,368,704 bytes) in size but the goal is 66.0 MB (69,206,016 bytes).  Make a backup of your file before going forward. Open the one you plan on using in a hex editor and make sure the ruler is extended to 2b.  


now click edit and choose goto, in a hex format paste 041fffd4. Make sure everything beyond this point is null (FF).  Once you confirm, highlight from the row directly under ( so from 0420000 on)


all the way to the end and hit delete.  Save the new file and confirm the new size is 66.0 MB (69,206,016 bytes)

Throw the new file through ibuild and everything should extract fine now.

sorry for the pic sizes

You can also use nandpro to make it the correct file size by "nandpro <original file name>.bin: -r64 <new file name>.bin" example: "nandpro originalnand.bin: -r64 66mbnand.bin" Much easier than having to hex edit anything.

[whackawookie]

QUOTE(ZprivateZ @ Apr 19 2010, 02:05 PM)

You can also use nandpro to make it the correct file size by "nandpro <original file name>.bin: -r64 <new file name>.bin" example: "nandpro originalnand.bin: -r64 66mbnand.bin" Much easier than having to hex edit anything.

you could yeah but already being at xbr and lpt connectors disconnected, this was the easiest option

[ZprivateZ]

QUOTE(whackawookie @ Apr 19 2010, 10:13 AM)

you could yeah but already being at xbr and lpt connectors disconnected, this was the easiest option

You don't need no lpt or usb/spi connected your reading from a dumped image (virtual nand) not from the nand itself on the board. If we were reading from the board the command would be "nandpro lpt:" or "nandpro usb:"

This post has been edited by ZprivateZ: Apr 19 2010, 03:19 PM

[whackawookie]

QUOTE(ZprivateZ @ Apr 19 2010, 02:17 PM)

You don't need no lpt or usb/spi connected your reading from a dumped image (virtual nand) not from the nand itself on the board. If we were reading from the board the command would be "nandpro lpt:" or "nandpro usb:"

bah, my bad. didn't know that was even an option with nandpro.

[cthompson019]

Used 0.032 with xbox1 patch & Easy_FreeBoot 0.5, flashed Zephyr with Flash360 and so far everything works perfect.  Will see how it stands to the kid test when she gets home from school and put's it through a few hours of heavy testing.

[jester]

Anyone with constant E79 should first double check their hacked SMC, then start over and rebuild, then reflash using XeLLouS or Flash360. If you continue to get E79, please PM me on IRC so I can get more info.