Hacking SNEEK v2

[SanGor]

latest rev, basicly just run the build_boot2.cmd copied my NAND to USB, the boot2_sd.bin as boot2.bin to SD and USB and the armboot.bin from the latest mini version to SD.

 

[mousex]

123

 

[betita_elfica]

build_all.cmd dont exist onlly exists SNEEK.cmd from DOWNLOADS of project code.google page. And then build_boot2_di.cmd and build_boot2.cmd in the svn.

But build_all.com ... dont exist and SNEEK.cmd with lastest revision dont create the boot2.bin

 

[mousex]

123

 

[fogbank]

But build_all.com ... dont exist and SNEEK.cmd with lastest revision dont create the boot2.bin

build_boot2.cmd creates boot2_usb.bin and boot2_sd.bin.

build_boot2_di.cmd creates di.bin.

The SNEEK.cmd and SNEEK-DI.cmd batch files don't seem to be properly updated.

Also be aware that the SNEEK batch files will modify the 0000000e.app file so you should not reuse the .app file between builds (always copy a new .app file if you use the SNEEK batch files).

 

[Det1re]

The SNEEK.cmd and SNEEK-DI.cmd batch files don't seem to be properly updated.

They weren't updated at all for the newer (>r44) revs.

 

[dancemonkey]

But build_all.com ... dont exist and SNEEK.cmd with lastest revision dont create the boot2.bin

build_boot2.cmd creates boot2_usb.bin and boot2_sd.bin.

build_boot2_di.cmd creates di.bin.

The SNEEK.cmd and SNEEK-DI.cmd batch files don't seem to be properly updated.

Also be aware that the SNEEK batch files will modify the 0000000e.app file so you should not reuse the .app file between builds (always copy a new .app file if you use the SNEEK batch files).

Thanks.

I assume you rename the boot2 you want. Also where does the di.bin file go on the SD?

 

[SanGor]

di.bin goes into the root

 

[dancemonkey]

Blue flashing light whatever I try

 

[Det1re]

Blue flashing light whatever I try

Incompatible SD card...

 

[dancemonkey]

Blue flashing light whatever I try

Incompatible SD card...

Has been working fine with other versions.

Do you stil have to edit es.c ?

 

[Blue-K]

Blue flashing light whatever I try

Incompatible SD card...

Has been working fine with other versions.

Well...then blame Team Twiizers then, I guess

. I think Crediar updated to the latest MINI-Source from them, and it's always a bit hit or miss there...see BootMii & SD-Cards...

 

[dancemonkey]

Blue flashing light whatever I try

Incompatible SD card...

Has been working fine with other versions.

Well...then blame Team Twiizers then, I guess

. I think Crediar updated to the latest MINI-Source from TT, and it's always a bit messy there...

I have another 4GB one. Fat32 format ok?

 

[Blue-K]

I have another 4GB one. Fat32 format ok?

Fat32. What else?

Yeah, it's alright...

 

[dancemonkey]

I have another 4GB one. Fat32 format ok?

Fat32. What else?

Yeah, it's alright...

3 SD cards all the same. Hmmmm.

 

[fogbank]

3 SD cards all the same. Hmmmm.

Make sure you are using the decrypted .app files from the IOS to make the .bin files, not the encrypted ones.

I've had blue flashing drive light with a compatible SD card when I inadvertently used the encrypted .app files.

 

[betita_elfica]

If i use decrypted .app dont create the boot2_sd.bin and boot2_usb.bin , only created if i put encrypted ones.

 

[SanGor]

you must use the DECRYPTED DI/ES modules OBVIOUSLY!
you shouldn't care so much about file extensions!

 

[dancemonkey]

3 SD cards all the same. Hmmmm.

Make sure you are using the decrypted .app files from the IOS to make the .bin files, not the encrypted ones.

I've had blue flashing drive light with a compatible SD card when I inadvertently used the encrypted .app files.

I think that was it . get a black screen now but no more blue flashing light. I assumed as the cmd file does not look for the .app that I needed the other ones. Just took the .app off the end. Just got to get rid of h black screen now

Do you know if we still have to comment in the usbhax thing?

Cheers!!

 

[mousex]

123