Dual Nand Squirt 2.0

Porque mi corona no arranca con la segunda nand? tiene xebuild flasheado.

Cuando enciendo la consola con la nand original todo perfecto
Cuando cambio a la segunda no enciende...
He probado todos los bitstream que hay

EDITO:
Cuando leo la segunda nand con autogg me da error, concretamente:
Size ERROR
Reading Nand wait...........
Header Error

Que estoy haciendo mal?

He seguido las indicaciones del team al pie de la letra:
First time nand reading (secondary nand empty):
To enable de Secondary reading/writin (rgh on):
-Disconnect the power cable of your console
-Press the sync button and reconnect the power cable
-Release the sync button and power on the console with power button, the fan will start very fast... (en este punto mi consola no enciende) turn off again the console
-start the writting/reading of secondary nand

claro que las instrucciones son para el 1.2, nose si varía mucho el asunto

Alguna sugerencia?

Saludos y gracias
sigo con mi problema, vuelvo a aportar mas detalles:
Corona V1
Squirt 2.0
Squirt QSB Corona
Nand pcb 16 mb Squirt

Archivos bitstream usados:
SQUIRT__corona_Reloaded_dual_nand_qsb
SQUIRT_corona_qsb_dual_nand
corona_dual_nand

Con todos el mismo resultado:
La nand ORIGINAL de la consola inicia sin problemas (el led del chip se enciende debilmente)
Pulso sync para cambiar de nand con la consola apagada, el led del chip se enciende fuertemente, Autogg detecta la nand,
Imagen

Cargo un dump de mi nand original, creo imagen xebuild, flasheo
Intento encender la consola mediante el panel frontal, pero esta ni se inmuta, solo hace el pitido pero nada mas

Que está pasando?
No CREO haber cometido ningun fallo en la instalacion, las soldaduras son de calidad. Utilizo estaño con 3 almas de flux decapante, por si fuera poco tambien añado un poco de flux liquido a los puntos de soldadura.

Adjunto algunas imágenes:
Imagen
Imagen
Imagen
Imagen


La instalacion RGH sin la dualnand funciona sin problemas
Tiene una media de tiempos de arranque entre 10 y 18 segundos

Agradezco la implicación de los usuarios y su ayuda.
Si esto se soluciona podría haber alguna compesación economica vía paypal. A nadie le viene mal 10 eurillos no?
Gracias por el soporte

Salu2!
virtualattack escribió:sigo con mi problema, vuelvo a aportar mas detalles:
Corona V1
Squirt 2.0
Squirt QSB Corona
Nand pcb 16 mb Squirt

Archivos bitstream usados:
SQUIRT__corona_Reloaded_dual_nand_qsb
SQUIRT_corona_qsb_dual_nand
corona_dual_nand

Con todos el mismo resultado:
La nand ORIGINAL de la consola inicia sin problemas (el led del chip se enciende debilmente)
Pulso sync para cambiar de nand con la consola apagada, el led del chip se enciende fuertemente, Autogg detecta la nand,
Imagen

Cargo un dump de mi nand original, creo imagen xebuild, flasheo
Intento encender la consola mediante el panel frontal, pero esta ni se inmuta, solo hace el pitido pero nada mas

Que está pasando?
No CREO haber cometido ningun fallo en la instalacion, las soldaduras son de calidad. Utilizo estaño con 3 almas de flux decapante, por si fuera poco tambien añado un poco de flux liquido a los puntos de soldadura.

Adjunto algunas imágenes:
Imagen
Imagen
Imagen
Imagen


La instalacion RGH sin la dualnand funciona sin problemas
Tiene una media de tiempos de arranque entre 10 y 18 segundos

Agradezco la implicación de los usuarios y su ayuda.
Si esto se soluciona podría haber alguna compesación economica vía paypal. A nadie le viene mal 10 eurillos no?
Gracias por el soporte

Salu2!


Hola

1º- Autogg te detecta la dual nand por que te muestra el mensaje Nand megas detectada pues la nand esta vacía, pero después de flashearla dale a leer de nuevo y te tiene que mostrar el mensaje Nand 16 mb detectada esa es la prueba de que tu nand se a flasheado bien, si te vuelve a mostrar el primer mensaje es porque no a flasheado la nand y por lo tanto sigue vacía, por lo que la consola nunca te arrancara con la segunda nand, solo con la original, saludos
Gracias por tu respuesta Casca.

La he flasheado varias veces y siempre obtengo lo mismo cuando quiero leerla (size error).

No se si es que me he saltado algun paso o he hecho algo mal

Edito:
No es problema de tension, a la nand le llega 2.84 V
virtualattack escribió:Gracias por tu respuesta Casca.

La he flasheado varias veces y siempre obtengo lo mismo cuando quiero leerla (size error).

No se si es que me he saltado algun paso o he hecho algo mal

Edito:
No es problema de tension, a la nand le llega 3.26 V


Puentea el PAD PU_END y flasheas la nand y luego lees con autogg a ver si te la reconoce como nand 16 mb, saludos.
me equivoque en el valor que puse.

a la segunda nand le llegan 2.84 V

He flasheado varias veces.. Xebuild, xell, retail... he borrado... he vuelto a flashear... etc y nunca reconoce los megas, es decir siempre se queda vacia

no lo entiendo
virtualattack escribió:me equivoque en el valor que puse.

a la segunda nand le llegan 2.84 V

He flasheado varias veces.. Xebuild, xell, retail... he borrado... he vuelto a flashear... etc y nunca reconoce los megas, es decir siempre se queda vacia

no lo entiendo


Pero as puenteado el PAD PU_EN, saludos.
casca escribió:
virtualattack escribió:me equivoque en el valor que puse.

a la segunda nand le llegan 2.84 V

He flasheado varias veces.. Xebuild, xell, retail... he borrado... he vuelto a flashear... etc y nunca reconoce los megas, es decir siempre se queda vacia

no lo entiendo


Pero as puenteado el PAD PU_EN, saludos.


Si Casca,

he probado de las dos formas

estoy bastante frustrado...

Edito:
No se si quitar el cable rojo del qsb que va de masa a una de las patillas del operacional
Puede ser por eso?
Imagen

Segun la imagen hay que hacer el puente en las coronas v1
EDITO:
He probado a quitar el cable y sin el no se puede cambiar a la nand original, además autogg no detecta el flasher

El flasheo de la segunda nand tengo que hacerlo con un bitstream específico y una vez hecho esto debo cambiarlo para el funcionamiento de la doble nand?
virtualattack escribió:...
Archivos bitstream usados:
SQUIRT__corona_Reloaded_dual_nand_qsb
SQUIRT_corona_qsb_dual_nand
corona_dual_nand

Con todos el mismo resultado:
...


The only bitstream that works with Squirt2.0 is "SQUIRT__corona_Reloaded_dual_nand_qsb"
The others will never work with it.

Can you measure the voltage on pad B (SMC reset) on squirt when you switch between nands?
pocoyo2 escribió:
virtualattack escribió:...
Archivos bitstream usados:
SQUIRT__corona_Reloaded_dual_nand_qsb
SQUIRT_corona_qsb_dual_nand
corona_dual_nand

Con todos el mismo resultado:
...


The only bitstream that works with Squirt2.0 is "SQUIRT__corona_Reloaded_dual_nand_qsb"
The others will never work with it.

Can you measure the voltage on pad B (SMC reset) on squirt when you switch between nands?


Un honor contar con el creador de este gran chip en nuestro foro.

Bienvenido pocoyo2
pocoyo2 escribió:
virtualattack escribió:...
Archivos bitstream usados:
SQUIRT__corona_Reloaded_dual_nand_qsb
SQUIRT_corona_qsb_dual_nand
corona_dual_nand

Con todos el mismo resultado:
...


The only bitstream that works with Squirt2.0 is "SQUIRT__corona_Reloaded_dual_nand_qsb"
The others will never work with it.

Can you measure the voltage on pad B (SMC reset) on squirt when you switch between nands?


Thanks a lot for your answer and sorry for my english!
Now I use SQUIRT__corona_Reloaded_dual_nand_qsb to program squirt 2.0

PAD B (original nand select): 3.29 V
PAD B (RGH nand select): 3.30 V

switching (one click to press sync): voltage drops and increase, fast!
some measures:
3.3V - drops to 3.09V when press - 3.3V
3.3 - 2.77 - 3.3
3.3 - 2.2 - 3.3
3.3 - 2.71 - 3.3
3.3 - 2.18 - 3.3
3.3 - 1.67 - 3.3
3.3 - 1.11 - 3.3

one thing, that i think is important. Sometimes when I was measuring, i need press sync button for a few seconds to switch to the original nand (first). This doesn't happend me before. when this happend, voltage drops to 0.44 V, every time

EDIT:
I can't write on second nand yet!
do you think that it may be corrupted?
Gracias pocoyo2 por aportar tus conocimientos en este foro, saludos.
zehenork escribió:
Un honor contar con el creador de este gran chip en nuestro foro.

Bienvenido pocoyo2


casca escribió:Gracias pocoyo2 por aportar tus conocimientos en este foro, saludos.


DEATH escribió:welcome pocoyo2.....


Thank you very much and thank you for supporting (and testing) squirt2.0.. :)

virtualattack escribió:Thanks a lot for your answer and sorry for my english!
Now I use SQUIRT__corona_Reloaded_dual_nand_qsb to program squirt 2.0

PAD B (original nand select): 3.29 V
PAD B (RGH nand select): 3.30 V

switching (one click to press sync): voltage drops and increase, fast!
some measures:
3.3V - drops to 3.09V when press - 3.3V
3.3 - 2.77 - 3.3
3.3 - 2.2 - 3.3
3.3 - 2.71 - 3.3
3.3 - 2.18 - 3.3
3.3 - 1.67 - 3.3
3.3 - 1.11 - 3.3

one thing, that i think is important. Sometimes when I was measuring, i need press sync button for a few seconds to switch to the original nand (first). This doesn't happend me before. when this happend, voltage drops to 0.44 V, every time

EDIT:
I can't write on second nand yet!
do you think that it may be corrupted?


Sorry for my english too, it's not my native language.. xD

PAD B is for resetting the SMC. While you press SYNC it must be LOW (0v) and goes HIGH (3,3v) once released.
Every time you switch between NANDs, CE_A and CE_B on NAND PCB must switch from HIGH to LOW and vice-versa (if CE_A is 3,3v CE_B is 0v). So, if you have CE_A and CE_B both at 3,3v there's something wrong on the installation.
Can you check PU_EN on PCB NAND? Try removing the solder bridge and see if it goes to 0v
thanks again for your answer pocoyo2!

it's a delight put into practice the concept of logic levels with you

welder's heat up, im going to test!

EDIT:
I remove the bridge on PU_EN pad and... here are the results

CE_A ; CE_B
2.89V ; -0.44V [mad] <-nand RGH selected
1.46V ; 3.11V <-primary nand selected

checked three times

EDIT:

I think that CE_A dont change to high logic state because voltage level is a little lower and for this I can't acces to write, but I dont know why...
Or maybe the problem is CE_B?
What do you think?

thanks genius!
Bienvenido a EOl "Pocoyo2", sin duda es un privilegio tenerte aqui con nosotros.
[tadoramo] [tadoramo] [tadoramo] [tadoramo]
breily escribió:Bienvenido a EOl "Pocoyo2", sin duda es un privilegio tenerte aqui con nosotros.


Thank you [ayay]

virtualattack escribió:thanks again for your answer pocoyo2!

it's a delight put into practice the concept of logic levels with you

welder's heat up, im going to test!

EDIT:
I remove the bridge on PU_EN pad and... here are the results

CE_A ; CE_B
2.89V ; -0.44V [mad] <-nand RGH selected
1.46V ; 3.11V <-primary nand selected

checked three times

EDIT:

I think that CE_A dont change to high logic state because voltage level is a little lower and for this I can't acces to write, but I dont know why...
Or maybe the problem is CE_B?
What do you think?

thanks genius!


Maybe there is a problem with installation of QSB. Can you check quick-solder points with a help of a magnifier and flux?
Here's an installation guideline of corona's. Check if wirings and connection are ok.

https://www.dropbox.com/s/93xj2cihzrprg ... L%20EN.pdf
do you prefer speak on spanish?
for me english its ok!

so, I checked all points on qsb with flux
some pictures:
Imagen
Imagen
Imagen


After that I check voltage on CE_A and CE_B when i switch between nands, and voltages are the same that before.
Also, I see that negative voltage come from pad C on QSB. When primary nand selected pad C has 0V, but when second nand its selected has -0.45V [mad] I dont understand why...
Como no me funcionaba la dualnand con qsb en corona v1, he probado a quitar el qsb y he instalado la segunda nand con cables.
ha sido un paso atras, puesto que ahora ni siquiera puedo arrancar la consola con la nand original, y la segunda nand sigo sin poder escribirla. Además el boton sync ahora no alterna bien entre las nands.

esto es un chiste [triston]

con el qsb al menos podia iniciar la nand original y cambiar a la secundaria sin problemas, aunque no pudiese escribirla

adjunto foto de la instalacion:

Imagen


A ver si alguien puede echarme una mano, porque es una pena que este gran chip no soporte dual nand en corona [buuuaaaa]
virtualattack escribió:Como no me funcionaba la dualnand con qsb en corona v1, he probado a quitar el qsb y he instalado la segunda nand con cables.
ha sido un paso atras, puesto que ahora ni siquiera puedo arrancar la consola con la nand original, y la segunda nand sigo sin poder escribirla. Además el boton sync ahora no alterna bien entre las nands.

esto es un chiste [triston]

con el qsb al menos podia iniciar la nand original y cambiar a la secundaria sin problemas, aunque no pudiese escribirla

...

A ver si alguien puede echarme una mano, porque es una pena que este gran chip no soporte dual nand en corona [buuuaaaa]


It's very strange that with qsb your dual nand won't work.
Can I ask to you what bitstream you flashed for "wired" dual nand? I know that it isn't released yet (public). And what about pull-up resistor "fix" like on Trinity's wired dual nand?

BTW this is a valid bitstream for wired dual nand on coronas. Almost you can try it

https://www.dropbox.com/s/o39ivky56lq9b ... ONE555.svf

let me know
Thanks GOD!
I miss you! haha you are a BOSS!

I have a question about pullup resistor... I need 1k or 10k?

Thanks 4 the bitstream... I tryed made some changes over qsb .svf obviously doesn't work

Tomorrow i get you some news about this case, my case, very extrange, i know... Like EVER :s

Thanks again!
When i finish this proyect i will make a donation for you! Seriously BRO!
See u tomorrow
1k, like on trinity's tutorial.
pocoyo2 escribió:1k, like on trinity's tutorial.


hey pocoyo2!
now i use the correct bitstream for corona dualnand wired. Also put a 1k resistor, and now i can switch between nands correctly

but i have the same problem like before, i cant write on second nand.
Yesterday I thought that nand maybe corrupted or damaged so I contacted with my provider and they send me a new squirt nand!

I have received today, and try with the wired instalation... SAME PROBLEM, cant write on second nand
First nand work correctly

I dont know what happend with my xbox! :S

EDIT1: if you want i can attach some pictures about full installation
thanks again bro
virtualattack escribió:
pocoyo2 escribió:1k, like on trinity's tutorial.


hey pocoyo2!
now i use the correct bitstream for corona dualnand wired. Also put a 1k resistor, and now i can switch between nands correctly

but i have the same problem like before, i cant write on second nand.
Yesterday I thought that nand maybe corrupted or damaged so I contacted with my provider and they send me a new squirt nand!

I have received today, and try with the wired instalation... SAME PROBLEM, cant write on second nand
First nand work correctly

I dont know what happend with my xbox! :S

EDIT1: if you want i can attach some pictures about full installation
thanks again bro


Put photos, so we can view if there's something strange...
I think that you have problems with Chip Enable of onboard nand. Maybe that one stays always "UP" and when you switch to external nand you have both enabled.
Can you tell me what voltage you have on CE_A and CE_B when you switch between nands?

Maybe (I don't know exactly all forum rules) you have to open a new thread about your problem
Ok, pocoyo2!

I go to test this pads and take some pictures.

Maybe i go to open a new thread
pocoyo2 escribió:
virtualattack escribió:
pocoyo2 escribió:1k, like on trinity's tutorial.


hey pocoyo2!
now i use the correct bitstream for corona dualnand wired. Also put a 1k resistor, and now i can switch between nands correctly

but i have the same problem like before, i cant write on second nand.
Yesterday I thought that nand maybe corrupted or damaged so I contacted with my provider and they send me a new squirt nand!

I have received today, and try with the wired instalation... SAME PROBLEM, cant write on second nand
First nand work correctly

I dont know what happend with my xbox! :S

EDIT1: if you want i can attach some pictures about full installation
thanks again bro


Put photos, so we can view if there's something strange...
I think that you have problems with Chip Enable of onboard nand. Maybe that one stays always "UP" and when you switch to external nand you have both enabled.
Can you tell me what voltage you have on CE_A and CE_B when you switch between nands?

Maybe (I don't know exactly all forum rules) you have to open a new thread about your problem


Hi pocoyo, its a Squirtv2 question, so we keep it here (Official Thread)

If you solve it and there's some interesting info i add it to first post.

Thx for support pocoyo ! ;)
pocoyo2 escribió:
virtualattack escribió:
pocoyo2 escribió:1k, like on trinity's tutorial.


hey pocoyo2!
now i use the correct bitstream for corona dualnand wired. Also put a 1k resistor, and now i can switch between nands correctly

but i have the same problem like before, i cant write on second nand.
Yesterday I thought that nand maybe corrupted or damaged so I contacted with my provider and they send me a new squirt nand!

I have received today, and try with the wired instalation... SAME PROBLEM, cant write on second nand
First nand work correctly

I dont know what happend with my xbox! :S

EDIT1: if you want i can attach some pictures about full installation
thanks again bro


Put photos, so we can view if there's something strange...
I think that you have problems with Chip Enable of onboard nand. Maybe that one stays always "UP" and when you switch to external nand you have both enabled.
Can you tell me what voltage you have on CE_A and CE_B when you switch between nands?

Maybe (I don't know exactly all forum rules) you have to open a new thread about your problem


Bueno, hago un breve resumen de mi caso hasta ahora

No consigo hacer funcionar una segunda nand en mi xbox.
Uso squirt 2.0 y la segunda nand tambien es squirt

He probado con el QSB
He probado haciendo la instalacion cableada, y utilizando el bitstream especifico para esta instalacion, aunque este bitstream aun no está publicado. Gracias pocoyo2 por compartirlo!

Tras probar los dos tipos de instalaciones y ver que la segunda nand nunca podia escribirla (autogg siempre me la detecta como: Nand Megas detectada...), pensé que quizás la nand podría estar corrupta o dañada.
Me puse en contacto con mi proveedor y me envió una totalmente gratuita. Gracias tambien a ellos!

El caso es que tambien he probado los dos metodos de instalacion con esta nand nueva, e igual, sigo en las mismas sin poder escribirla.
La primera nand funciona sin problemas. El boton sync tambien alterna perfectamente entre ambas.

Tengo un monton de fotos de todas las instalaciones que he probado, pero voy a poner la ultima que he hecho. La segunda nand que me enviaron con la instalacion por cables:
Imagen
Imagen


Aqui dejo unas mediciones que he hecho de los pads CE_A y CE_B en la segunda nand

Cuando la segunda nand esta seleccionada: CE_A = 0.6V ; CE_B = 0
Cuando la primera nand esta seleccionada: CE_A = 0 ; CE_B = 3.36 V
Good.
Try this:
- Desolder the points J and K from squirt
- Check voltages on those pads while switching. They must be "J" NOT "K" (eg: if J is 0, K is 1)
- Check voltages on CE_A and CE_B on nand PCB
- Put reports here
pocoyo2 escribió:Good.
Try this:
- Desolder the points J and K from squirt
- Check voltages on those pads while switching. They must be "J" NOT "K" (eg: if J is 0, K is 1)
- Check voltages on CE_A and CE_B on nand PCB
- Put reports here


J and K desoldered.
All measurements with pads desoldered

second nand selected:
J = 0
K = 3.36 V
CE_A = 0.16 V
CE _B = 1.56 V

primary nand selected:
J = 3.36 V
K = 0
CE_A = 0.20 V
CE _B = 1.55 V

thank a lot again pocoyo!

EDITO:
lo explico en spanish pa que quede mas claro.
Algunas veces cuando procedo a hacer las mediciones creo que se cambia de nand automaticamente, porque el led del chip varia de intensidad como cuando se pulsa el boton sync.
Da igual que primero toque gnd y despues el punto a medir o viceversa. Cuando le parece cambia de nand "aleatoriamente" y las tensiones se vuelven inestables... Es mas dificil explicarlo que entenderlo
Pero como ya digo, esto solo ocurre algunas veces y no entiendo el por qué
Remove the blue wire, if you use a resistor between vcc and pad C (sync) like in picture.
I was wrong asking you to check voltage on CE_A, because that pad on wired installation is not connected.
The values you reported indicates that both chip and bitstream are OK.
You have to resolder J to CE_B and K to CE (the point under the mmotherboard). Then you must check if CE (on the motherboard) is 0 with primary nand and 3.3v with secondary nand.
Tell me results
pocoyo2 escribió:Remove the blue wire, if you use a resistor between vcc and pad C (sync) like in picture.
I was wrong asking you to check voltage on CE_A, because that pad on wired installation is not connected.
The values you reported indicates that both chip and bitstream are OK.
You have to resolder J to CE_B and K to CE (the point under the mmotherboard). Then you must check if CE (on the motherboard) is 0 with primary nand and 3.3v with secondary nand.
Tell me results


EDIT (bad previous measures, sorry)
3.35V second nand
1.72V primary nand
Try this:
- switch to primary nand (squirt led off)
- WITHOUT unplug power supply, desolder the wire from pad B on squirt
- switch to secondary nand (squirt led on)
- try read it
pocoyo2 escribió:Try this:
- switch to primary nand (squirt led off)
- WITHOUT unplug power supply, desolder the wire from pad B on squirt
- switch to secondary nand (squirt led on)
- try read it


i can read!
try write??

EDIT:
after I follow your steps I tried write xebuild on second nand (led on), but when i go to read again, autogg dont detect size (Nand Megas detectada....)
Repeat steps I wrote. Try writing freeboot instead of reading
pocoyo2 escribió:Repeat steps I wrote. Try writing freeboot instead of reading


ok, go to solder smc reset, and try again!

EDIT:
now when i desolder pad B primary nand switch to secondary, automatically...

EDIT 2:
cant write. autogg: Ha ocurrido un error en el proceso

EDIT 3:
Repeat process three or four times... try write second nand before read... but dont work...
At this point, post detailed photos..
About chip, Nand, Autogg? Or everyrhing?
sorry for the delay
I made a video, and I had to record four times because unusual cases happened
I didn't work in any of the cases
I'll keep on trying

http://youtu.be/bufpvidI7Pc

EDIT:
I forgot say that in this case the xbox dont work with the original nand, but normally work perfect
Good work.
Can you make a snapshot of ALE, RE, CLE, WE, WP, CE, R/B and the 8 DATA bits?
Also, have you removed the blue wire?

PS: maybe you have to re-check connections from motherboard to nand pcb
I have to remove a wire from B pad to PU_EN?
pocoyo2 escribió:Remove the blue wire, if you use a resistor between vcc and pad C (sync) like in picture.


Yes. If you put resistor like you already did, the wire from B to PU_EN must not be connected
ok!

now i have a problem with a pad on mb. pad where I/06 connect its break.

Can I solder on the resistor or this doesnt work? try to fix the point?

second from right... :S

Adjuntos

It does't work. You must fix it. The resistor is connected by the via to the nand on top. :(
pocoyo2 escribió:It does't work. You must fix it. The resistor is connected by the via to the nand on top. :(


I think its fixed

Imagen
Imagen


Now I go to try write second nand again

EDIT:
Finally I CAN WRITE ON SECOND NAND! maybe the pad that i broke was damaged before...
after write xebuild I read and autogg detect 16mb nand!

The problem now its that xbox dont start with any nands

Thanks for support pocoyo! I want make a donation for you
So autogg recognizes both nands WITHOUT remove SMC_RST wire?
yes!

EDIT:
why xbox cant boot up with any nands?
Break pad is not the problem because I bridge the resistor with the same point where I connect de second nand, o top of mb

I could boot from retail nand without problems before write successfully second nand...

EDIT 2:
Im really happy
After many tests, my Corona V1 run with two nands.
Squirt 2.0 + Squirt 16 Mb PCB (wired installation)

Later i will upload a video booting from retail nand and secondary nand

Thanks a lot Pocoyo2! I really want to speak with you on private

Regards! [sonrisa]
Good work man! [plas]
What was the problem?
I'm happy you have done the trick! Now, if you want, you can make some pics so I can make the missing "dual nand wiring install on corona" tutorial [jaja]

edit: if you want you can send me a pm
the problem was smc reset. simply desoldered from pad B and xbox boot from primary and secondary nand.

now i go to clean a llitle the installation and take some pics!

Edit:
without smc reset solder on a pad B, I think that boot from RGH nand its more slow that in a normal RGH installation.
Maybe if we fix this, boots from RGH nand will be faster!
Without SMC Reset you'll notbe safe on LIVE, imho
69 respuestas
1, 2